Bug#641153: document Built-Using field for binary packages
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
On the contrary, internally it's really very close to other dependency
fields... it's treated like a "union"-dependency field (like
> Since the only purpose of this paragraph is to allow to list pipe-separated
> alternatives, I propose to not add Built-Using to that paragraph, as in my
> undersanding it is not expected to list alternatives.
It's not even allowed since it's a "union"-dependency field.
Raphaël Hertzog ◈ Debian Developer
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHertzog.fr (Français)