[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: DEP-5 and files with white spaces

Am Mittwoch, den 01.02.2012, 14:20 -0800 schrieb Russ Allbery:
> Benjamin Drung <bdrung@debian.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
> happy).

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.

> The general way to specify information for a file name that contains
> whitespace is to use wildcards to match the whitespace, which means that
> you can't disambiguate from other files that only differ in the places
> where whitespace is present.

I don't like the idea of abusing a wildcard if the files could be
specified more precisely.

> Out of curiosity, have you run across a case where this matters, or were
> you asking because it's a theoretical hole?  It's definitely a theoretical
> hole, but one of the reasons why we didn't spend more time on it was that
> everyone was dubious that the case would arise in a real-world situation.

I haven't run across an actual case. This case just popped into my mind
and I wondered how to cover this case.

Benjamin Drung
Debian & Ubuntu Developer

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: