(debian-policy.info)Additional source packages used to build the binary - Built-Using

---

Prev: Relationships between source and binary packages - Build-Depends Build-Depends-Indep Build-Depends-Arch Build-Conflicts Build-Conflicts-Indep Build-Conflicts-Arch Up: Declaring relationships between packages

---

Enter node , (file) or (file)node

7.8 Additional source packages used to build the binary - ‘Built-Using’
=======================================================================

Some binary packages incorporate parts of other packages when built but
do not have to depend on those packages.  Examples include linking with
static libraries or incorporating source code from another package
during the build.  In this case, the source packages of those other
packages are part of the complete source (the binary package is not
reproducible without them).

When the license of either the incorporated parts or the incorporating
binary package requires that the full source code of the incorporating
binary package be made available, the ‘Built-Using’ field must list the
corresponding source package for any affected binary package
incorporated during the build, (1) including an “exactly equal” (“=”)
version relation on the version that was used to build that version of
the incorporating binary package.  (2)

This causes the Debian archive to retain the versions of the source
packages that were actually incorporated.  In particular, if the
versions of the incorporated parts are updated but the incorporating
binary package is not rebuilt, the older versions of the incorporated
parts will remain in the archive in order to satisfy the license.

A package using the source code from the gcc-4.6-source binary package
built from the gcc-4.6 source package would have this field in its
control file:

     Built-Using: gcc-4.6 (= 4.6.0-11)

A package including binaries from grub2 and loadlin would have this
field in its control file:

     Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)

This field should not be added solely for purposes other than satisfying
license or DFSG requirements to provide full source code.  In
particular, it should not be added solely to enable finding packages
that should be rebuilt against newer versions of their build
dependencies.

   ---------- Footnotes ----------

   (1) ‘Build-Depends’ in the source package is not adequate since it
(rightfully) does not document the exact version used in the build.

   (2) The archive software might reject packages that refer to
non-existent sources.