Charles Plessy <ple...@debian.org> writes: > I just realised that we forgot to document this field.
> How about the following patch. > diff --git a/policy.sgml b/policy.sgml > index 4dec04c..d2e506e 100644 > --- a/policy.sgml > +++ b/policy.sgml > @@ -2753,6 +2753,7 @@ Package: libc6 > <item><qref id="f-VCS-fields"><tt>Vcs-Browser</tt>, > <tt>Vcs-Git</tt>, et al.</qre > <item><qref > id="f-Standards-Version"><tt>Standards-Version</tt></qref> (recommend > <item><qref id="sourcebinarydeps"><tt>Build-Depends</tt> et > al</qref></item> > + <item><qref id="f-Package-List"><tt>Package-List</tt></qref></item> > <item><qref id="f-Checksums"><tt>Checksums-Sha1</tt> > and <tt>Checksums-Sha256</tt></qref> (mandatory)</item> > <item><qref id="f-Files"><tt>Files</tt></qref> (mandatory)</item> > @@ -3812,6 +3813,19 @@ Checksums-Sha256: > </taglist> > </p> > </sect1> > + > + <sect1 id="f-Package-List"> > + <heading><tt>Package-List</tt></heading> > + > + <p> > + Multiline field listing all the packages that can be built from > + the source package. The first line of the field value is empty. > + Each one of the next lines describe one binary package, by listing > + its name, type, section and priority separated by spaces. There > + are two possible package types: binary package (<tt>deb</tt>) or > + micro binary package (<tt>udeb</tt>). > + </p> > + </sect1> > </sect> > > <sect> > Does anybody know if this field mandatory or optional ? Seconded, once that question has been resolved. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87623bledo....@windlord.stanford.edu
