+ udebs (stripped-down binary packages used by the Debian Installer) do
+ not comply with all of the requirements discussed here. See the
+ for more
+ information about them.
+
@@ -1322,9 +1330,9 @@ zope.
The package installation scripts should avoid producing
output which is unnecessary for the user to see and
should rely on dpkg to stave off boredom on
- the part of a user installing many packages. This means,
- amongst other things, using the --quiet option on
- install-info.
+ the part of a user installing many packages. This means,
+ amongst other things, not passing the --verbose
+ option to update-alternatives.
@@ -1729,7 +1737,7 @@ zope.
/closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i
Then all of the bug numbers listed will be closed by the
- archive maintenance script (katie) using the
+ archive maintenance software (dak) using the
version of the changelog entry.
This information is conveyed via the Closes field
@@ -2153,7 +2161,7 @@ zope.
The architectures we build on and build for are determined
by make variables using the
- utility dpkg-architecture.
+ utility dpkg-architecture.
You can determine the Debian architecture and the GNU style
architecture specification string for the build architecture as
well as for the host architecture. The build architecture is
@@ -2671,6 +2679,7 @@ Package: libc6
- Description (mandatory)
- Homepage
- Built-Using
+ - Package-Type
@@ -2751,6 +2760,7 @@ Package: libc6
- Vcs-Browser, Vcs-Git, et al.
- Standards-Version (recommended)
- Build-Depends et al
+ - Package-List (recommended)
- Checksums-Sha1
and Checksums-Sha256 (mandatory)
- Files (mandatory)
@@ -3801,6 +3811,34 @@ Checksums-Sha256:
+
+
+ Package-List
+
+
+ Multiline field listing all the packages that can be built from
+ the source package, considering every architecture. The first line
+ of the field value is empty. Each one of the next lines describes
+ one binary package, by listing its name, type, section and priority
+ separated by spaces. Fifth and subsequent space-separated items
+ may be present and parsers must allow them. See the
+ Package-Type field for a list of
+ package types.
+
+
+
+
+ Package-Type
+
+
+ Simple field containing a word indicating the type of package:
+ deb for binary packages and udeb for micro binary
+ packages. Other types not defined here may be indicated. In
+ source package control files, the Package-Type field
+ should be omitted instead of giving it a value of deb, as
+ this value is assumed for paragraphs lacking this field.
+
+
@@ -3931,8 +3969,7 @@ Checksums-Sha256:
Programs called from maintainer scripts should not normally
have a path prepended to them. Before installation is
started, the package management system checks to see if the
- programs ldconfig,
- start-stop-daemon, install-info,
+ programs ldconfig, start-stop-daemon,
and update-rc.d can be found via the
PATH environment variable. Those programs, and any
other program that one would expect to be in the
@@ -6705,7 +6742,7 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)
The shlibs control files for all the
packages currently installed on the system. These are
normally found
- in /var/lib/dpkg/info/*.symbols, but
+ in /var/lib/dpkg/info/*.shlibs, but
packages should not rely on this and instead should
use dpkg-query --control-path package
shlibs if for some reason these files need to be
@@ -10459,18 +10496,23 @@ name ["syshostname"]:
The install-info program maintains a directory of
- installed info documents in /usr/share/info/dir for
- the use of info readers.
- It was previously necessary for packages installing info
- documents to run install-info from maintainer
- scripts. This is no longer necessary. The installation
- system now uses dpkg triggers.
-
- This file must not be included in packages. Packages containing
- info documents should depend on dpkg (>= 1.15.4) |
- install-info to ensure that the directory file is properly
- rebuilt during partial upgrades from Debian 5.0 (lenny) and
- earlier.
+ installed info documents in /usr/share/info/dir for the
+ use of info readers. This file must not be included in packages
+ other than install-info.
+
+
+
+ install-info is automatically invoked when
+ appropriate using dpkg triggers. Packages other than
+ install-info should not invoke
+ install-info directly and should not
+ depend on, recommend, or suggest install-info
+ for this purpose.
+
+
+
+ Info readers requiring the /usr/share/info/dir file
+ should depend on install-info.
@@ -10837,12 +10879,6 @@ END-INFO-DIR-ENTRY
dpkg, dselect et al. and the way
they interact with packages.
-
- It also documents the interaction between
- dselect's core and the access method scripts it
- uses to actually install the selected packages, and describes
- how to create a new access method.
-
This manual does not go into detail about the options and
usage of the package building and installation tools. It
@@ -10852,10 +10888,7 @@ END-INFO-DIR-ENTRY
The utility programs which are provided with dpkg
- for managing various system configuration and similar issues,
- such as update-rc.d and
- install-info, are not described in detail here -
- please see their man pages.
+ not described in detail here, are documented in their man pages.
@@ -10875,25 +10908,9 @@ END-INFO-DIR-ENTRY
Binary packages (from old Packaging Manual)
- The binary package has two main sections. The first part
- consists of various control information files and scripts used
- by dpkg when installing and removing. See [.
- ]
-
-
- The second part is an archive containing the files and
- directories to be installed.
+ See and [.
]
-
- In the future binary packages may also contain other
- components, such as checksums and digital signatures. The
- format for the archive is described in full in the
- deb(5) man page.
-
-
-
Creating package files -
dpkg-deb
@@ -11195,55 +11212,7 @@ END-INFO-DIR-ENTRY
- dpkg-buildpackage is a script which invokes
- dpkg-source, the debian/rules
- targets clean, build and
- binary, dpkg-genchanges and
- gpg (or pgp) to build a signed
- source and binary package upload.
-
-
-
- It is usually invoked by hand from the top level of the
- built or unbuilt source directory. It may be invoked with
- no arguments; useful arguments include:
-
- -uc, -us
- -
-
- Do not sign the .changes file or the
- source package .dsc file, respectively.
-
- -psign-command
- -
-
- Invoke sign-command instead of finding
- gpg or pgp on the PATH.
- sign-command must behave just like
- gpg or pgp.
-
- -rroot-command
- -
-
- When root privilege is required, invoke the command
- root-command. root-command
- should invoke its first argument as a command, from
- the PATH if necessary, and pass its
- second and subsequent arguments to the command it
- calls. If no root-command is supplied
- then dpkg-buildpackage will use
- the fakeroot command, which is sufficient
- to build most packages without actually requiring root
- privileges.
-
- -b, -B
- -
-
- Two types of binary-only build and upload - see
- .
-
-
-
+ See .
@@ -11367,23 +11336,10 @@ END-INFO-DIR-ENTRY
- This program is usually called by package-independent
- automatic building scripts such as
- dpkg-buildpackage, but it may also be called
- by hand.
-
-
-
- It is usually called in the top level of a built source
- tree, and when invoked with no arguments will print out a
- straightforward .changes file based on the
- information in the source package's changelog and control
- file and the binary and source packages which should have
- been built.
+ See .
-
dpkg-parsechangelog - produces parsed
@@ -11391,12 +11347,7 @@ END-INFO-DIR-ENTRY
- This program is used internally by
- dpkg-source et al. It may also occasionally
- be useful in debian/rules and elsewhere. It
- parses a changelog, debian/changelog by default,
- and prints a control-file format representation of the
- information in it to standard output.
+ See .
@@ -11407,10 +11358,7 @@ END-INFO-DIR-ENTRY
- This program can be used manually, but is also invoked by
- dpkg-buildpackage or debian/rules to set
- environment or make variables which specify the build and host
- architecture for the package building process.
+ See .