On Thu, Nov 10, 2011 at 03:19:07PM +0100, Vít Ondruch wrote: > Dne 10.11.2011 13:57, Scott Schmit napsal(a): > > Yes, but the purpose of URL encoding is to reach resources that are > named using reserved characters. So, for the filename you showed above, > the correct URL would be: > file:///usr/lib/ruby/gems/1.8/doc/pg-0.11.0/ri/PGconn/internal_encoding%253d-i.yaml > ^^^^^ > > This is because the % character is reserved. Had the file name been > "internal_encoding=.yaml", the URL would have been: > file:///usr/lib/ruby/gems/1.8/doc/pg-0.11.0/ri/PGconn/internal_encoding%3d-i.yaml > ^^^ > > Hence "broken". > Is the tool that accesses these files able to find them currently? If so I agree with Vit that it's not broken. The filename is being transformed for a particular tool to use. The filesystem allows it because it doesn't contain Null bytes. The guidelines don't have to be changed to accomodate it because the characters are all encoded in utf-8. As you point out, the tool in question may well not be using proper URLs internally but we do not make the demand that any of our tools only use URLs to access files. > > It doesn't matter how it would look if you'd like to refer to the filename > using URL, the truth is that its the filename RI is using. This [1] is the code > if you are interested and this [2] is the oldest version I can find on GitHub. > > The rpmlint says just that much about the name: > > This package contains a file whose path contains something that looks like an > unexpanded macro; this is often the sign of a misspelling. Please check your > specfile. > > So this is not the case. The name is perfectly fine at the end. No need to > worry. I believe I looked at a different rubygem with a similar rpmlint warning and came to the same conclusion. -Toshio
Attachment:
pgplZ9ixkMNjN.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
