Bug#641153: document Built-Using field for binary packages
Le Sun, Sep 11, 2011 at 08:32:33AM +0200, Raphael Hertzog a écrit :
> On Sun, 11 Sep 2011, Charles Plessy wrote:
> > This adds Built-Using in §5.6.10 (“Package interrelationship fields: Depends,
> > Pre-Depends, Recommends, Suggests, Breaks, Conflicts, Provides, Replaces,
> > Enhances”). In Policy's chapter 5, the fields in that list are documented to
> > be present in source package control files (§5.2) and binary package control
> > files (§5.3). However, dpkg-source does not allow the field in source package
> > control files (allowed => ALL_PKG, see scripts/Dpkg/Control/Fields.pm).
>
> I don't understand your reasoning... "Depends" is also "allowed =>
> ALL_PKG" which means allowed in "control" in the .deb, and in a package
> entry in debian/control (and in a Packages file and in
> /var/lib/dpkg/status).
My point is that if the Built-Using field is not to be used elsewhere than in
binary control files, I propose, if and only if this is consensual, to submit
an amended patch that makes this clear in the Policy.
[And about how I made a wrong statement about dpkg's internals in my previous
email: I quickly took Installed-Size as an exemple of field that is not found
in source control files to reverse-engeneer what ALL_PKG means, saw that it is
"allowed => ALL_PKG & ~CTRL_INFO_PKG" and that the field above, Homepage is
"allowed => ALL_SRC | ALL_PKG", and wrongly concluded that ALL_SRC meant source
and ALL_PKG meant binary. I hope that the rest of my answer to Ansgar is more
useful, and also welcome feedback about it. Sorry for the noise.]
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
Reply to: