DESCRIPTIONConfiguration classes used by Config::Model
ArchitectureIf a program needs to specify an architecture specification string in some place, it should select one of the strings provided by dpkg-architecture -L. The strings are in the format os-arch, though the OS part is sometimes elided, as when the OS is Linux. A package may specify an architecture wildcard. Architecture wildcards are in the format any (which matches every architecture), os-any, or any-cpu. For more details, see Debian policy <http://www.debian.org/doc/debian-policy/ch-customized-programs.html#s-arch-spec> Mandatory. Type string.
Multi-ArchThis field is used to indicate how this package should behave on a multi-arch installations. This field should not be present in packages with the Architecture: all field. Optional. Type enum. choice: 'same', 'foreign', 'allowed'.
Here are some explanations on the possible values:
- allows reverse-dependencies to indicate in their Depends field that they need a package from a foreign architecture, but has no effect otherwise.
- the package is not co-installable with itself, but should be allowed to satisfy the dependency of a package of a different arch from itself.
- the package is co-installable with itself, but it must not be used to satisfy the dependency of any package of a different architecture from itself.
SectionOptional. Type uniline.
PriorityOptional. Type enum. choice: 'required', 'important', 'standard', 'optional', 'extra'.
EssentialOptional. Type boolean.
DependsOptional. Type list of uniline.
RecommendsOptional. Type list of uniline.
SuggestsOptional. Type list of uniline.
EnhancesOptional. Type list of uniline.
Pre-DependsOptional. Type list of uniline.
BreaksOptional. Type list of uniline.
ConflictsOptional. Type list of uniline.
ProvidesOptional. Type list of uniline.
ReplacesOptional. Type list of uniline.
Built-UsingSome 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 a required part of the complete source (the binary package is not reproducible without them).
A Built-Using field must list the corresponding source package for any such binary package incorporated during the build, including an ``exactly equal'' (``='') version relation on the version that was used to build that binary package.
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) I<< Optional. Type list of uniline. >>
Package-Type - The type of the package, if not a regular Debian oneIf this field is present, the package is not a regular Debian package, but either a udeb generated for the Debian installer or a tdeb containing translated debconf strings. Optional. Type enum. choice: 'tdeb', 'udeb'.
Note: Package-Type is migrated with '$xc' and with $xc => ""- XC-Package-Type""
XC-Package-Type - The type of the package, if not a regular Debian oneIf this field is present, the package is not a regular Debian package, but either a udeb generated for the Debian installer or a tdeb containing translated debconf strings. Deprecated Optional. Type enum. choice: 'tdeb', 'udeb'.
SynopsisMandatory. Type uniline.
DescriptionMandatory. Type string.
HomepageOptional. Type uniline.
XB-Python-VersionDeprecated Optional. Type uniline.
XB-Ruby-Versionsindicate the versions of the interpreter supported by the library. Optional. Type uniline.
Build-ProfilesA list of lists of (optionally negated) profile names, forming a conjunctive normal form expression in the same syntax as in the Build-Depends field. Optional. Type uniline.
- Dominique Dumont
- 2010,2011 Dominique Dumont