Am Mittwoch, den 01.02.2012, 23:31 +0100 schrieb Jakub Wilk: > * Russ Allbery <r...@debian.org>, 2012-02-01, 14:20: > >>DEP-5 is nice, but how can I specify a license for a file with white > >>spaces? For example you want to specify that the file "foo/file > >>one.bar" is licensed under ISC, but "foo/file_one.bar" is licensed > >>under GPL. How can you do that? > > > >No, that distinction isn't representable. > > This one is representable. You can take advantage of the fact the "the > last paragraph that matches a particular file applies to it": > > | Files: foo/file?one.bar > | License: ISC > | > | Files: foo/file_one.bar > | License: GPL > > That said, you _can_ construct even more contrived examples which are > unrepresentable, e.g. by replacing "_" with a tab. > > >The general way to specify information for a file name that contains > >whitespace is to use wildcards to match the whitespace, > > That works only if you can stand ugliness of such Files fields.
True words. For example, the eclipse source package has files with spaces in it using ? instead of spaces does look ugly. -- Benjamin Drung Debian & Ubuntu Developer
signature.asc
Description: This is a digitally signed message part
