X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=d81891c7c5f2b52af5c26cebabde59dc4b2d9014;hb=4f33957d200f7b37a81b5632dbd77d69d4c71007;hp=10e626babf857a9c1b25e56444ae3d75f9f12e2c;hpb=bce4b938b4e603a7bceeaf2ad31d007d0a9dcb43;p=debian%2Fdebian-policy.git

diff --git a/policy.sgml b/policy.sgml
index 10e626b..d81891c 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -1729,7 +1729,7 @@ zope.
 /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i
 	      </example>
 	      Then all of the bug numbers listed will be closed by the
-	      archive maintenance script (<prgn>katie</prgn>) using the
+	      archive maintenance software (<prgn>dak</prgn>) using the
 	      <var>version</var> of the changelog entry.
 	  </footnote>
 	  This information is conveyed via the <tt>Closes</tt> field
@@ -2671,6 +2671,7 @@ Package: libc6
 	    <item><qref id="f-Description"><tt>Description</tt></qref> (mandatory)</item>
 	    <item><qref id="f-Homepage"><tt>Homepage</tt></qref></item>
 	    <item><qref id="built-using"><tt>Built-Using</tt></qref></item>
+	    <item><qref id="f-Package-Type"><tt>Package-Type</tt></qref></item>
 	  </list>
 	</p>
 
@@ -2751,6 +2752,7 @@ Package: libc6
 	  <item><qref id="f-VCS-fields"><tt>Vcs-Browser</tt>, <tt>Vcs-Git</tt>, et al.</qref></item>
 	  <item><qref id="f-Standards-Version"><tt>Standards-Version</tt></qref> (recommended)</item>
 	  <item><qref id="sourcebinarydeps"><tt>Build-Depends</tt> et al</qref></item>
+	  <item><qref id="f-Package-List"><tt>Package-List</tt></qref> (recommended)</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>
@@ -3801,6 +3803,34 @@ 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, 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.
+	  </p>
+	</sect1>
+
+	<sect1 id="f-Package-Type">
+	  <heading><tt>Package-Type</tt></heading>
+
+	  <p>
+	    Simple field containing a word indicating the type of package:
+	    <tt>deb</tt> for binary packages and <tt>udeb</tt> for micro binary
+	    packages.  Other types not defined here may be indicated.  In
+	    source package control files, the <tt>Package-Type</tt> field
+	    should be omitted instead of giving it a value of <tt>deb</tt>, as
+	    this value is assumed for paragraphs lacking this field.
+	  </p>
+	</sect1>
       </sect>
 
       <sect>
@@ -10837,12 +10867,6 @@ END-INFO-DIR-ENTRY
 	<prgn>dpkg</prgn>, <prgn>dselect</prgn> et al. and the way
 	they interact with packages.</p>
 
-      <p>
-	It also documents the interaction between
-	<prgn>dselect</prgn>'s core and the access method scripts it
-	uses to actually install the selected packages, and describes
-	how to create a new access method.</p>
-
       <p>
 	This manual does not go into detail about the options and
 	usage of the package building and installation tools.  It