Bug#431813: support for wrapped Uploaders should now be mandatory
Package: debian-policy
Version: 3.7.2.2
Severity: wishlist
Now that etch has released, the dpkg in stable supports unwrapping a
wrapped Uploaders field in debian/control. This fix was made in dpkg
1.13.14, uploaded to experimental on 2006-02-12.
Accordingly, we can now elevate the should support in policy to a must
support to match the other fields in debian/control that support
wrapping.
I also continue to find the specification of field wrapping less than
obvious for the relationship fields; section 7.1 still doesn't say
explicitly that fields may be wrapped. So at the risk of addressing
multiple issues in one patch, I also added some additional language to
that section to be more explicit.
Comments?
--- orig/policy.sgml
+++ mod/policy.sgml
@@ -2392,16 +2392,10 @@
</p>
<p>
Any parser that interprets the Uploaders field in
- <file>debian/control</file> should permit it to span multiple
- lines<footnote>
- In the future, the Uploaders field in
- <file>debian/control</file> (but not other control files)
- will be permitted to span multiple lines and interpreting
- a multi-line Uploaders field shall be mandatory.
- </footnote>. Line breaks in an Uploaders field that spans
- multiple lines are not significant and the semantics of
- the field are the same as if the line breaks had not been
- present.
+ <file>debian/control</file> must permit it to span multiple
+ lines. Line breaks in an Uploaders field that spans multiple
+ lines are not significant and the semantics of the field are
+ the same as if the line breaks had not been present.
</p>
</sect1>
@@ -3883,13 +3877,16 @@
Whitespace may appear at any point in the version
specification subject to the rules in <ref
id="controlsyntax">, and must appear where it's necessary to
- disambiguate; it is not otherwise significant. For
+ disambiguate; it is not otherwise significant. All of the
+ relationship fields may span multiple lines. For
consistency and in case of future changes to
<prgn>dpkg</prgn> it is recommended that a single space be
used after a version relationship and before a version
number; it is also conventional to put a single space after
each comma, on either side of each vertical bar, and before
- each open parenthesis.
+ each open parenthesis. When wrapping a relationship field, it
+ is conventional to do so after a comma and before the space
+ following that comma.
</p>
<p>
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-- no debconf information
Reply to: