формат главного управляющего файла пакетов исходного кода Debian (Debian source packages' master control file format)
BINARY FIELDS
Note that the Priority, Section and Homepage fields can also be
in a binary paragraph to override the global value from the
source package.
Package: binary-package-name (required)
This field is used to name the binary package name. The
same restrictions as to a source package name apply.
Package-Type: deb|udeb|type
This field defines the type of the package. udeb is for
size-constrained packages used by the debian installer.
deb is the default value, it is assumed if the field is
absent. More types might be added in the future.
Architecture: arch|all|any (required)
The architecture specifies on which type of hardware this
package runs. For packages that run on all architectures,
use the any value. For packages that are architecture
independent, such as shell and Perl scripts or
documentation, use the all value. To restrict the packages
to a certain set of architectures, specify the
architecture names, separated by a space. It's also
possible to put architecture wildcards in that list (see
dpkg-architecture(1) for more information about them).
Build-Profiles: restriction-formula
This field specifies the conditions for which this binary
package does or does not build. To express that
condition, the same restriction formula syntax from the
Build-Depends field is used.
If a binary package paragraph does not contain this field,
then it implicitly means that it builds with all build
profiles (including none at all).
In other words, if a binary package paragraph is annotated
with a non-empty Build-Profiles field, then this binary
package is generated if and only if the condition
expressed by the conjunctive normal form expression
evaluates to true.
Essential: yes|no
Build-Essential: yes|no
Multi-Arch: same|foreign|allowed|no
Tag: tag-list
Description: short-description (recommended)
These fields are described in the deb-control(5) manual
page, as they are copied literally to the control file of
the binary package.
Depends: package-list
Pre-Depends: package-list
Recommends: package-list
Suggests: package-list
Breaks: package-list
Enhances: package-list
Replaces: package-list
Conflicts: package-list
Provides: package-list
Built-Using: package-list
These fields declare relationships between packages. They
are discussed in the deb-control(5) manpage. When these
fields are found in debian/control they can also end with
a trailing comma (since dpkg 1.10.14), have architecture
specifications and restriction formulas which will all get
reduced when generating the fields for deb-control(5).
Subarchitecture: value
Kernel-Version: value
Installer-Menu-Item: value
These fields are used by the debian-installer in udebs and
are usually not needed. See
/usr/share/doc/debian-installer/devel/modules.txt from the
debian-installer package for more details about them.
