Le Thu, Jan 10, 2013 at 03:58:31AM +0100, Guillem Jover a écrit :
>
> On Thu, 2013-01-10 at 07:32:54 +0900, Charles Plessy wrote:
> >
> > <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
> > describe
> > one binary package, by listing its name, type, section and
> > priority
> > separated by spaces. See the
> > <qref id="f-Package-Type">Package-Type</qref> field for a list
> > of
> > package types.
> > </p>
>
> Parsers should handle other possible values being appended (still
> separater by spaces).
>
> > I have one more question about Package-List: will it always list only binary
> > packages, or can it also list source packages as suggested when the field
> > was
> > proposed ?
>
> It will only list binary packages, not all the information for the
> source package is currently available from other fields in the .dsc
> file, but it could be exported through those (Priority, Section) if
> the need arises. Its name is a bit unfortunate though, it should have
> been named something like Binary-List as a replacement for Binary, but
> oh well, I guess it's too late now...
Thanks, how about the following ?
index 10e626b..2b7f4a2 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -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,8 @@ 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>
(recommended)</item>
+ <item><qref id="f-Package-Type"><tt>Package-Type</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>
@@ -3801,6 +3804,30 @@ 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. Other space-separated values may be added.
+ 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.
+ </p>
+ </sect1>
</sect>
Cheers,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130111120521.ge13...@falafel.plessy.net
