On Sat, Aug 21 2010, Russ Allbery wrote:
> Ben Finney writes:
>> Lars Wirzenius writes:
>
>>> * Have one copyright statement per Copyright field, and have multiple
>>> instances of the field.
>
>> This is my preference, and what I've been doing in my packages.
>
> Unfortunately, this creates rea
Lars Wirzenius writes:
> On su, 2010-08-22 at 08:00 +1000, Ben Finney wrote:
> > Could we take advantage of the natural “©” marker to indicate each
> > copyright statement?
>
> That's an interesting idea, but would people in general find it easy or
> difficult to write that character? (I'd have t
On Sun, Aug 22, 2010 at 11:36:54AM +1200, Lars Wirzenius wrote:
> On su, 2010-08-22 at 08:00 +1000, Ben Finney wrote:
> > Could we take advantage of the natural “©” marker to indicate each
> > copyright statement?
> That's an interesting idea, but would people in general find it easy or
> difficul
On la, 2010-08-21 at 16:41 -0700, Russ Allbery wrote:
> Ideally, I'd like to just copy and paste upstream's copyright statements
> into debian/copyright and maybe do some compaction, which leads me to
> prefer a free-form field. Do we think that people are going to want to
> parse and extract indi
On Sun, Aug 22, 2010 at 11:36:54AM +1200, Lars Wirzenius wrote:
> On su, 2010-08-22 at 08:00 +1000, Ben Finney wrote:
> > Could we take advantage of the natural “©” marker to indicate each
> > copyright statement?
>
> That's an interesting idea, but would people in general find it easy or
> diffic
Lars Wirzenius writes:
> On su, 2010-08-22 at 08:00 +1000, Ben Finney wrote:
>> Could we take advantage of the natural “©” marker to indicate each
>> copyright statement?
> That's an interesting idea, but would people in general find it easy or
> difficult to write that character? (I'd have to c
On su, 2010-08-22 at 08:00 +1000, Ben Finney wrote:
> Could we take advantage of the natural “©” marker to indicate each
> copyright statement?
That's an interesting idea, but would people in general find it easy or
difficult to write that character? (I'd have to copy-paste it, for
instance, since
Russ Allbery writes:
> Ben Finney writes:
> > Lars Wirzenius writes:
>
> >> * Have one copyright statement per Copyright field, and have multiple
> >> instances of the field.
>
> > This is my preference, and what I've been doing in my packages.
>
> Unfortunately, this creates real challenges fo
On la, 2010-08-21 at 08:32 -0400, Stephen Leake wrote:
> Lars Wirzenius writes:
>
> > Files has a list
> > of values (currently comma-separated, but I propose to make it
> > white-space separated),
>
> File names can have spaces. Not common, but possible. I guess such file
> names would need to
On la, 2010-08-21 at 15:47 +0300, George Danchev wrote:
> I just wonder what this list would be meant to serves which can't be deemed
> suitable for -mentors. Many upstreams (regardless they have any preliminary
> packages of their software or not) already use -mentors for entering Debian
> one
Ben Finney writes:
> Lars Wirzenius writes:
>> * Have one copyright statement per Copyright field, and have multiple
>> instances of the field.
> This is my preference, and what I've been doing in my packages.
Unfortunately, this creates real challenges for parsers. I've written a
few RFC 532
On Sat, Aug 21, 2010 at 15:47:46 +0300, George Danchev wrote:
> I just wonder what this list would be meant to serves which can't be deemed
> suitable for -mentors. Many upstreams (regardless they have any preliminary
> packages of their software or not) already use -mentors for entering Debian
Lars Wirzenius writes:
> On la, 2010-08-21 at 02:15 -0700, Russ Allbery wrote:
> > What happens when the copyright statement is longer than a line?
[…]
> Good point. I see at least thw following possible solutions:
[…]
> * Have one copyright statement per Copyright field, and have multiple
> in
Lars Wirzenius writes:
> On pe, 2010-08-20 at 14:55 +0200, Stefano Zacchiroli wrote:
> > Now, I've no idea if the above would be appropriate for the upstream
> > front desk or not. I leave it up to you to decide whether it's worth
> > trying or not.
>
> I think a debian-upstre...@lists.debian.org
Lars Wirzenius writes:
> Files has a list
> of values (currently comma-separated, but I propose to make it
> white-space separated),
File names can have spaces. Not common, but possible. I guess such file
names would need to be quoted?
--
-- Stephe
--
To UNSUBSCRIBE, email to debian-projec
On la, 2010-08-21 at 02:15 -0700, Russ Allbery wrote:
> What happens when the copyright statement is longer than a line? I have a
> bunch of those, such as:
Good point. I see at least thw following possible solutions:
* Keep one line per copyright statement, but make the lines be long.
(This is
On la, 2010-08-21 at 01:58 -0700, Russ Allbery wrote:
> > How would that tie in with updating it via the normal policy process? I
> > thought we'd keep the file in the debian-policy package for future
> > updates.
>
> I was assuming that's how we'd get to a 1.1 version. I haven't read DEP-0
> rec
Lars Wirzenius writes:
> While wording this, I realized that we have more cases: Files has a list
> of values (currently comma-separated, but I propose to make it
> white-space separated), and Copyright and maybe other fields have a list
> of values one per line. I took the liberty of taking this
On la, 2010-08-21 at 20:32 +1200, Lars Wirzenius wrote:
> I'm OK with saying that multiline fields should use the Description
> markup, especially noting Charles's point about only using the long
> description part, when appropriate. This simplifies things quite a lot.
> I'll word a concrete patch
Lars Wirzenius writes:
> On pe, 2010-08-20 at 17:05 -0700, Russ Allbery wrote:
>> I think a better approach would be to, once the document has settled
>> down, publish it with a version number and give that version of the
>> document a permanent URL. So, for instance, we would publish DEP-5 1.0
On pe, 2010-08-20 at 17:05 -0700, Russ Allbery wrote:
> I think a better approach would be to, once the document has settled down,
> publish it with a version number and give that version of the document a
> permanent URL. So, for instance, we would publish DEP-5 1.0 and give it a
> URL something
Lars Wirzenius writes:
> On pe, 2010-08-20 at 16:52 -0700, Steve Langasek wrote:
>> The fact that we're both expressing this in terms of "preference"
>> means, I think, both that this doesn't meet Lars's "wave of opposition"
>> standard and that we're not definitely in bikeshed territory. :) I
>
On pe, 2010-08-20 at 16:52 -0700, Steve Langasek wrote:
> The fact that we're both expressing this in terms of "preference" means, I
> think, both that this doesn't meet Lars's "wave of opposition" standard and
> that we're not definitely in bikeshed territory. :) I support Lars in
> deciding this
23 matches
Mail list logo
