Bug#533852: debian-policy: Allow Binary field to span over multiple lines
Raphaël Hertzog hert...@debian.org writes: In response to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494714 I would like that the policy be updated to allow the Binary field in .dsc and .changes to span over multiple lines. Sorry about the delay in getting to this. Here is somewhat different proposed wording that cleans up the rest of this section. I'm looking for seconds for this wording. diff --git a/policy.sgml b/policy.sgml index 3c5a22d..c618afd 100644 --- a/policy.sgml +++ b/policy.sgml @@ -3261,29 +3261,27 @@ Package: libc6 headingttBinary/tt/heading p - This field is a list of binary packages. + This field is a list of binary packages. Its syntax and + meaning varies depending on the control file in which it + appears. /p p - When it appears in the file.dsc/file file it is the list - of binary packages which a source package can produce. It - does not necessarily produce all of these binary packages - for every architecture. The source control file doesn't - contain details of which architectures are appropriate for - which of the binary packages. - /p - - p - When it appears in a file.changes/file file it lists the - names of the binary packages actually being uploaded. + When it appears in the file.dsc/file file, it lists binary + packages which a source package can produce, separated by + commasfootnote + A space after each comma is conventional. + /footnote. It may span multiple lines. The source package + does not necessarily produce all of these binary packages for + every architecture. The source control file doesn't contain + details of which architectures are appropriate for which of + the binary packages. /p p - The syntax is a list of binary packages separated by - commasfootnote - A space after each comma is conventional. - /footnote. Currently the packages must be separated using - only spaces in the file.changes/file file. + When it appears in a file.changes/file file, it lists the + names of the binary packages being uploaded, separated by + whitespace (not commas). It may span multiple lines. /p /sect1 -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
On Fri, Aug 7, 2009 at 13:33:57 -0700, Russ Allbery wrote: Raphaël Hertzog hert...@debian.org writes: In response to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494714 I would like that the policy be updated to allow the Binary field in .dsc and .changes to span over multiple lines. Sorry about the delay in getting to this. Here is somewhat different proposed wording that cleans up the rest of this section. I'm looking for seconds for this wording. Looks good to me, seconded. Cheers, Julien signature.asc Description: Digital signature
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
On Fri, 2009-08-07 at 13:33:57 -0700, Russ Allbery wrote: Raphaël Hertzog hert...@debian.org writes: In response to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494714 I would like that the policy be updated to allow the Binary field in .dsc and .changes to span over multiple lines. Sorry about the delay in getting to this. Here is somewhat different proposed wording that cleans up the rest of this section. I'm looking for seconds for this wording. diff --git a/policy.sgml b/policy.sgml index 3c5a22d..c618afd 100644 --- a/policy.sgml +++ b/policy.sgml @@ -3261,29 +3261,27 @@ Package: libc6 headingttBinary/tt/heading p - This field is a list of binary packages. + This field is a list of binary packages. Its syntax and + meaning varies depending on the control file in which it + appears. /p p - When it appears in the file.dsc/file file it is the list - of binary packages which a source package can produce. It - does not necessarily produce all of these binary packages - for every architecture. The source control file doesn't - contain details of which architectures are appropriate for - which of the binary packages. - /p - - p - When it appears in a file.changes/file file it lists the - names of the binary packages actually being uploaded. + When it appears in the file.dsc/file file, it lists binary + packages which a source package can produce, separated by + commasfootnote + A space after each comma is conventional. + /footnote. It may span multiple lines. The source package + does not necessarily produce all of these binary packages for + every architecture. The source control file doesn't contain + details of which architectures are appropriate for which of + the binary packages. /p p - The syntax is a list of binary packages separated by - commasfootnote - A space after each comma is conventional. - /footnote. Currently the packages must be separated using - only spaces in the file.changes/file file. + When it appears in a file.changes/file file, it lists the + names of the binary packages being uploaded, separated by + whitespace (not commas). It may span multiple lines. /p /sect1 Seconded. regards, guillem signature.asc Description: Digital signature
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
Guillem Jover guil...@debian.org writes: On Fri, 2009-08-07 at 13:33:57 -0700, Russ Allbery wrote: Raphaël Hertzog hert...@debian.org writes: In response to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494714 I would like that the policy be updated to allow the Binary field in .dsc and .changes to span over multiple lines. Sorry about the delay in getting to this. Here is somewhat different proposed wording that cleans up the rest of this section. I'm looking for seconds for this wording. Seconded. Thanks! That's two, so I've applied this for the next Policy release. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
Hi! On Sat, 2009-06-20 at 16:29:48 -0700, Don Armstrong wrote: On Sun, 21 Jun 2009, Raphaël Hertzog wrote: --- a/policy.sgml +++ b/policy.sgml @@ -3276,7 +3276,9 @@ Package: libc6 commasfootnote A space after each comma is conventional. /footnote. Currently the packages must be separated using - only spaces in the file.changes/file file. + only spaces in the file.changes/file file. The list can span This should be changed to read file, and may wrap. Seconded (with Don's wording change). regards, guillem signature.asc Description: Digital signature
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
On Sat, 20 Jun 2009, Russ Allbery wrote: Raphaël Hertzog hert...@debian.org writes: In response to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494714 I would like that the policy be updated to allow the Binary field in .dsc and .changes to span over multiple lines. This would be the first field in .dsc and .changes that would permit continuation lines. [...] continuation lines there. I think the current system, where all the tools that read debian/control and generate other files from it unwrap all the lines, makes a lot of technical sense. Yes, and the reason for the multi-line support in this field is a technical reason (line too long for gpg/email transport) so I don't want to allow it everywhere but only here. Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
Raphael Hertzog hert...@debian.org writes: Yes, and the reason for the multi-line support in this field is a technical reason (line too long for gpg/email transport) so I don't want to allow it everywhere but only here. Sorry, I clearly didn't read the original report thoroughly enough. I understand better now. Wouldn't Build-Depends potentially have the same problem for packages with particularly heavy dependencies? I suppose we could cross that bridge when we come to it, though, and realistically Binary is a lot longer. Anyway, seconded in principal, although I agree with the wording commentary previously posted. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
On Sat, 20 Jun 2009, Don Armstrong wrote: On Sun, 21 Jun 2009, Raphaël Hertzog wrote: --- a/policy.sgml +++ b/policy.sgml @@ -3276,7 +3276,9 @@ Package: libc6 commasfootnote A space after each comma is conventional. /footnote. Currently the packages must be separated using - only spaces in the file.changes/file file. + only spaces in the file.changes/file file. The list can span This should be changed to read file, and may wrap. Are you sure that it would convey the information that the wrapping is allowed in both .dsc and .changes ? If yes, I'm fine with it. The wording was just a suggestion, I'm ok with any variant as long at it means the same. :) Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
Package: debian-policy Version: 3.8.2.0 Severity: wishlist Tags: patch In response to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494714 I would like that the policy be updated to allow the Binary field in .dsc and .changes to span over multiple lines. Here's a suggested patch: --- a/policy.sgml +++ b/policy.sgml @@ -3276,7 +3276,9 @@ Package: libc6 commasfootnote A space after each comma is conventional. /footnote. Currently the packages must be separated using - only spaces in the file.changes/file file. + only spaces in the file.changes/file file. The list can span + over multiple lines if needed, in that case the linefeed + characters are treated like spaces. /p /sect1 Cheers, Raphael. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
On Sun, 21 Jun 2009, Raphaël Hertzog wrote: --- a/policy.sgml +++ b/policy.sgml @@ -3276,7 +3276,9 @@ Package: libc6 commasfootnote A space after each comma is conventional. /footnote. Currently the packages must be separated using - only spaces in the file.changes/file file. + only spaces in the file.changes/file file. The list can span This should be changed to read file, and may wrap. + over multiple lines if needed, in that case the linefeed + characters are treated like spaces. The above is superfluous. It cannot be separated just by newlines, because it needs a leading space or tab, and Policy 5.1 already specifies how to do that. Don Armstrong -- A Democracy lead by politicians and political parties, fails. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533852: debian-policy: Allow Binary field to span over multiple lines
Raphaël Hertzog hert...@debian.org writes: In response to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494714 I would like that the policy be updated to allow the Binary field in .dsc and .changes to span over multiple lines. This would be the first field in .dsc and .changes that would permit continuation lines. I'd rather not do this one-by-one if we're going to make a change here, particularly since it's already confusing what fields permit continuation lines and which don't. Currently, we have a fairly clean separation in that some lines in debian/control can be wrapped, but nothing in *.dsc, *.changes, or DEBIAN/control may be wrapped except the fields whose content includes newlines in the format. Before we change that fairly clean separation, I'd like to know where our long-term direction is here and whether we should be planning to support wrapping every field. Given that *.dsc, *.changes, and DEBIAN/control are not usually edited by humans and are generally only interpreted by programs, I question the point of adding complexity to everything else in Debian to support continuation lines there. I think the current system, where all the tools that read debian/control and generate other files from it unwrap all the lines, makes a lot of technical sense. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
