Hi, Quoting Charles Plessy (2014-08-06 07:41:40) > what do you think about the patch I sent to the Policy, for describing the > syntax of the current optional fields of the Packages-List field ? Do you > think that modifications are needed ? Would you second it ? > > https://bugs.debian.org/756835 > > Have a nice day,
I had worded it a bit differently: diff --git a/policy.sgml b/policy.sgml index fbbe4a3..840951c 100644 --- a/policy.sgml +++ b/policy.sgml @@ -3824,10 +3824,17 @@ Checksums-Sha256: the source package, considering every architecture. The first line of the field value is empty. Each one of the next lines describes one binary package, by listing its name, type, section and priority - separated by spaces. Fifth and subsequent space-separated items - may be present and parsers must allow them. See the - <qref id="f-Package-Type">Package-Type</qref> field for a list of - package types. + separated by spaces. + See the <qref id="f-Package-Type">Package-Type</qref> field for a + list of package types. + Fifth and subsequent space-separated items are key/value pairs of + the form <tt>key=value1,value2</tt>. The currently used keys are + the <tt>arch</tt> key which lists the architectures a binary + package builds for and the <tt>profile</tt> key which lists the + build profiles a binary package builds in. + <footnote>The key/value syntax for all fields after the fourth was + introduced in <prgn>dpkg</prgn> version <tt>1.17.7</tt> in + <em>Jessie</em>.</footnote> </p> </sect1> cheers, josch -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140806060316.19236.55079@hoothoot