X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=b27aecf52b9fa482cbaac628d4d835594c68517c;hb=0371de0c0aee5687e571260faf6298c2b5c7104f;hp=43926534da730cac53b3f8dcd6ae16b0e9f1f441;hpb=fadd5e8b67183327a7b3c0f9872396242e784875;p=debian%2Fdebian-policy.git
diff --git a/policy.sgml b/policy.sgml
index 4392653..b27aecf 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -158,6 +158,14 @@
distributed in some other way or is intended for local use
only.
+
+
+ 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
@@ -1908,7 +1916,8 @@ zope.
The following targets are required and must be implemented
by debian/rules: clean, binary,
- binary-arch, binary-indep, and build.
+ binary-arch, binary-indep, build,
+ build-arch and build-indep.
These are the targets called by dpkg-buildpackage.
@@ -2153,7 +2162,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
@@ -2649,7 +2658,6 @@ Package: libc6
- Source (mandatory)
- Maintainer (mandatory)
- Uploaders
- - DM-Upload-Allowed
- Section (recommended)
- Priority (recommended)
- Build-Depends et al
@@ -2672,6 +2680,7 @@ Package: libc6
- Description (mandatory)
- Homepage
- Built-Using
+ - Package-Type
@@ -2748,13 +2757,13 @@ Package: libc6
- Version (mandatory)
- Maintainer (mandatory)
- Uploaders
- - DM-Upload-Allowed
- Homepage
- Vcs-Browser, Vcs-Git, et al.
- Standards-Version (recommended)
- Build-Depends et al
+ - Package-List (recommended)
- Checksums-Sha1
- and Checksums-Sha256 (recommended)
+ and Checksums-Sha256 (mandatory)
- Files (mandatory)
@@ -2807,7 +2816,7 @@ Package: libc6
- Closes
- Changes (mandatory)
- Checksums-Sha1
- and Checksums-Sha256 (recommended)
+ and Checksums-Sha256 (mandatory)
- Files (mandatory)
@@ -3741,28 +3750,19 @@ Checksums-Sha256:
- In the .dsc file, these fields should list all
+ In the .dsc file, these fields list all
files that make up the source package. In
- the .changes file, these fields should list all
+ the .changes file, these fields list all
files being uploaded. The list of files in these fields
must match the list of files in the Files field.
-
+
DM-Upload-Allowed
- Indicates that Debian Maintainers may upload this package to
- the Debian archive. The only valid value is yes. If
- the field DM-Upload-Allowed: yes is present in the
- source section of the source control file of the most recent
- version of a package in unstable or experimental, the Debian
- archive will accept uploads of this package signed with a key
- in the Debian Maintainer keyring. See the General
- Resolution for more
- details.
+ Obsolete, see below.
@@ -3812,6 +3812,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.
+
+
-
It is noted in the status database as being in a
- sane state, namely not installed (any conffiles
+ sane state, namely "Not-Installed" (any conffiles
it may have are ignored, rather than being
removed by dpkg). Note that
disappearing packages do not have their prerm
@@ -4547,7 +4596,7 @@ fi
No attempt is made to unwind after errors during
configuration. If the configuration fails, the package is in
- a "Failed Config" state, and an error message is generated.
+ a "Half-Configured" state, and an error message is generated.
@@ -5358,7 +5407,7 @@ Depends: foo-data (>= 1.2-3)
dpkg does not know of any files it still
contains, it is considered to have "disappeared". It will
be marked as not wanted on the system (selected for
- removal) and not installed. Any conffiles
+ removal) and "Not-Installed". Any conffiles
details noted for the package will be ignored, as they
will have been taken over by the overwriting package. The
package's postrm script will be run with a
@@ -6623,7 +6672,7 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)
The shlibs system
- The shlibs system is an simpler alternative to
+ The shlibs system is a simpler alternative to
the symbols system for declaring dependencies for
shared libraries. It may be more appropriate for C++
libraries and other cases where tracking individual symbols is
@@ -6694,7 +6743,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
@@ -8038,33 +8087,28 @@ Reloading description configuration...done.
- Packages which provide the ability to view/show/play,
- compose, edit or print MIME types should register themselves
- as such following the current MIME support policy.
+ Packages which provide programs to view/show/play, compose, edit or
+ print MIME types should register them as such by placing a file in
+ format (RFC 1524) in the directory
+ /usr/lib/mime/packages/. The file name should be the
+ binary package's name.
The mime-support package provides the
- update-mime program which allows packages to
- register programs that can show, compose, edit or print
- MIME types.
-
-
-
- Packages containing such programs must register them
- with update-mime as documented in . They should not depend
- on, recommend, or suggest mime-support. Instead,
- they should just put something like the following in the
- postinst and postrm scripts:
-
-
- if [ -x /usr/sbin/update-mime ]; then
- update-mime
- fi
-
+ update-mime program, which integrates these
+ registrations in the /etc/mailcap file, using dpkg
+ triggers
+ Creating, modifying or removing a file in
+ /usr/lib/mime/packages/ using maintainer scripts will
+ not activate the trigger. In that case, it can be done by calling
+ dpkg-trigger --no-await /usr/lib/mime/packages from
+ the maintainer script after creating, modifying, or removing
+ the file.
+ .
+ Packages using this facility should not depend on,
+ recommend, or suggest mime-support.
-
@@ -10453,18 +10497,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.
@@ -10831,12 +10880,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
@@ -10846,10 +10889,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.
@@ -10869,25 +10909,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
@@ -11189,55 +11213,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 .
@@ -11361,23 +11337,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
@@ -11385,12 +11348,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 .
@@ -11401,10 +11359,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 .
@@ -12093,6 +12048,11 @@ END-INFO-DIR-ENTRY
there is a time, after it has been diverted but before
dpkg has installed the new version, when the file
does not exist.
+
+
+ Do not attempt to divert a conffile, as dpkg does not
+ handle it well.
+