[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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 <hertzog@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
>  	  <heading><tt>Binary</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
> +	    commas<footnote>
> +		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
> -	    commas<footnote>
> -		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

Attachment: signature.asc
Description: Digital signature


Reply to: