Re: DEP-5 and files with white spaces
Benjamin Drung <email@example.com> writes:
> Am Mittwoch, den 01.02.2012, 14:20 -0800 schrieb Russ Allbery:
>> Benjamin Drung <firstname.lastname@example.org> writes:
>> > 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. There was some earlier
>> discussion about that, and the conclusion reached was that it was a rare
>> case that wasn't worth making the syntax more complicated (after various
>> more complicated syntaxes were tossed around without making anyone very
> Is it to complex to have a syntax that is similar to what the shell
> does? Two solutions pop into my mind. Please let me know, why these are
> not use. You can point me to previous discussions.
> Idea 1: Use a escape sequence for specifying a whitespace (e.g. "\ " for
> a space).
> Idea 2: Allow quotation marks.
Not a solution on its own. What about a file named foo" bar' baz?
For a worst case what about files with newlines?