X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=1390cf41c5e0d69d6de6135e806776c1c181c73d;hb=f812bda88f43e6af288b21d37a5a6e34d675190d;hp=628d8dfd27609bd174538ed63ec79d3ddc56b0de;hpb=095aa5909d4f173d5f6ff4fd603a688f6f094ab2;p=debian%2Fdebian-policy.git
diff --git a/policy.sgml b/policy.sgml
index 628d8df..1390cf4 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.
@@ -3961,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
@@ -6735,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
@@ -10489,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.
@@ -10896,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
@@ -11216,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 .