Adam Borowski writes:
> It looks like there is not a single such filename in all sources, anywhere
> in unstable (for x in *.tar.*z*;do tar tf "$x";done). Even lletters-media
> ships its data with English names and links them at build.
Oh, cool, thank you for checking! I think we can safely no
On Fri, Feb 10, 2012 at 11:50:10AM +0100, Adam Borowski wrote:
> On Thu, Feb 09, 2012 at 11:05:25PM -0800, Russ Allbery wrote:
> > Note that another case that I don't think has been discussed, but which is
> > probably more common than embedded quote marks, is a filename that's
> > invalid UTF-8 (s
* Charles Plessy , 2012-02-11, 12:06:
For the encoding, this is not a problem limited to the machine-readable
format. If the Debian copyright file is in an encoding A, and one file
has a name or is in a directory that has a name in an encoding B that
can not be represented in A, and that there
Le Fri, Feb 10, 2012 at 10:05:55AM -0800, Russ Allbery a écrit :
> Jakub Wilk writes:
> > * Russ Allbery , 2012-02-09, 23:05:
>
> >> Note that another case that I don't think has been discussed, but which
> >> is probably more common than embedded quote marks, is a filename that's
> >> invalid UT
* Paul Wise , 2012-02-11, 08:35:
Of course, it's source packages that matter, can't check them that
easily. Could someone who has all the sources downloaded and unpacked
check? My box that has them decided to not heed wake-on-lan.
Just look at the Contents-source files:
ftp://ftp.debian.org/
On Fri, Feb 10, 2012 at 6:50 PM, Adam Borowski wrote:
> Of course, it's source packages that matter, can't check them that easily.
> Could someone who has all the sources downloaded and unpacked check? My box
> that has them decided to not heed wake-on-lan.
Just look at the Contents-source files
Jakub Wilk writes:
> * Russ Allbery , 2012-02-09, 23:05:
>> Note that another case that I don't think has been discussed, but which
>> is probably more common than embedded quote marks, is a filename that's
>> invalid UTF-8 (straight ISO 8859-1, for example). That's also not
>> representable in o
* Russ Allbery , 2012-02-09, 23:05:
Note that another case that I don't think has been discussed, but which
is probably more common than embedded quote marks, is a filename that's
invalid UTF-8 (straight ISO 8859-1, for example). That's also not
representable in our typical debian/copyright fil
On Thu, Feb 09, 2012 at 11:05:25PM -0800, Russ Allbery wrote:
> Wouter Verhelst writes:
> > On Thu, Feb 09, 2012 at 11:01:00AM +0100, Goswin von Brederlow wrote:
>
> >> Not a solution on its own.
>
> > Actually, I think it's a perfectly workable solution.
>
> >> What about a file named foo" bar
On Thu, Feb 09, 2012 at 11:05:25PM -0800, Russ Allbery wrote:
> Note that another case that I don't think has been discussed, but which is
> probably more common than embedded quote marks, is a filename that's
> invalid UTF-8 (straight ISO 8859-1, for example).
Do these even happen anymore? Looki
Wouter Verhelst writes:
> On Thu, Feb 09, 2012 at 11:01:00AM +0100, Goswin von Brederlow wrote:
>> Not a solution on its own.
> Actually, I think it's a perfectly workable solution.
>> What about a file named foo" bar' baz?
>>
>> For a worst case what about files with newlines?
> Unless these
On Thu, Feb 09, 2012 at 11:01:00AM +0100, Goswin von Brederlow wrote:
> > Idea 2: Allow quotation marks.
>
> Not a solution on its own.
Actually, I think it's a perfectly workable solution.
> What about a file named foo" bar' baz?
>
> For a worst case what about files with newlines?
Unless the
On Thu, Feb 09, 2012 at 07:38:29PM +0300, Andrew Shadura wrote:
> Hello,
>
> On Thu, 09 Feb 2012 11:01:00 +0100
> Goswin von Brederlow wrote:
>
> > > 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 w
Hello,
On Thu, 09 Feb 2012 11:01:00 +0100
Goswin von Brederlow wrote:
> > 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?
You can double the delimiter to embed it into a string, like this:
"f
Benjamin Drung writes:
> Am Mittwoch, den 01.02.2012, 14:20 -0800 schrieb Russ Allbery:
>> Benjamin Drung 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
Le Thu, Feb 02, 2012 at 09:50:09AM +0900, Charles Plessy a écrit :
>
> 1) DEP 5 and directory/file names with spaces
>(http://lists.debian.org/debian-devel/2009/06/msg00155.html)
>
> My summary is that the participants were quite divided on whether separating
> the list of files by spaces or
Le Wed, Feb 01, 2012 at 11:44:36PM +0100, Benjamin Drung a écrit :
>
> 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.
Hi Benjamin,
You can refer to
Am Mittwoch, den 01.02.2012, 14:56 -0800 schrieb Russ Allbery:
> Benjamin Drung writes:
> > Am Mittwoch, den 01.02.2012, 14:49 -0800 schrieb Russ Allbery:
>
> >> Yeah, both of those were among the other syntax proposals that were
> >> suggested, and I think one of them was in the document at one
Benjamin Drung writes:
> Am Mittwoch, den 01.02.2012, 14:49 -0800 schrieb Russ Allbery:
>> Yeah, both of those were among the other syntax proposals that were
>> suggested, and I think one of them was in the document at one point.
>> Using backslash is probably the easiest, although it does make
Am Mittwoch, den 01.02.2012, 14:49 -0800 schrieb Russ Allbery:
> Benjamin Drung writes:
>
> > 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.
>
>
Benjamin Drung writes:
> 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
>
Am Mittwoch, den 01.02.2012, 23:31 +0100 schrieb Jakub Wilk:
> * Russ Allbery , 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
Am Mittwoch, den 01.02.2012, 14:20 -0800 schrieb Russ Allbery:
> Benjamin Drung 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 lice
Jakub Wilk writes:
> 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
Oh, hey, yes, good point.
--
Russ Allbery (
* Russ Allbery , 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'
Benjamin Drung 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 repres
26 matches
Mail list logo
