Re: DEP 5 and directory/file names with spaces
You know, this is probably a stupid question, but what's wrong with
separating file patterns with newlines, as continuations?
Files: a b
c
d e f
g.*
To me it looks more readable, no escaping or quotes are necessary, at
the expense of being a bit more difficult to type than quoting (though
definitely not as difficult as escaping every space). We know that
newlines can't be part of a filename (right?!) so it seems appropriate
to do it this way.
In most cases, the Files: field will only be one or two lines per
paragraph, so it doesn't make sense *not* to do it this way.
Further, how often are masks like these really used in practice? In my
experience working on Debian Perl packages, most of the time we just
use simple masks like:
Files: inc/*
And often it's just different sets of files (ie, Module::Install or
ppport.h files) that have different copyright information that we'd
need to represent in the file anyway.
Are there examples of packages with really complicated copyright
patterns we can use, so we have a real-world example we can base our
work on? After all, the intent of this format is to be useful with
what we already have, and what we think we might have, rather than
some contrived examples that aren't likely to be encountered much, if
at all...
Cheers,
Jonathan
On Mon, Jun 8, 2009 at 3:14 AM, Lars Wirzenius<liw@liw.fi> wrote:
> su, 2009-06-07 kello 20:07 -0700, Steve Langasek kirjoitti:
>> In other words, the real question is: which of these is easier for your
>> hypothetical user to read?:
>>
>> space-separated
>> Files: a\ b c d\ e\ f g.*
>>
>> comma-separated
>> Files: a\,b, c, d\,e\,f, g.*
>
> url-encoded:
>
> Files: a%2Cb c d%2Ce%2Cf g.*
> Files: a%20b c d%20e%20f g.*
>
>> For my part I'm actually inclined to say that the latter is more readable,
>> but let's get the rationale right. :)
>
> I rather think they're all unreadable. URL encoding at least makes it
> easy to see each pattern separately from the others.
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: