From: Russ Allbery Date: Mon, 2 Feb 2009 05:16:05 +0000 (-0800) Subject: Disambiguate "installed" and "present" for package states X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=2bd9de0d4db8a0f933277cf69819dac8cfaee41c;p=debian%2Fdebian-policy.git Disambiguate "installed" and "present" for package states Replace some "installed" and "present" descriptions of packages with "unpacked" to more clearly distinguish between the unpacked and configured states and be more consistent with the verbs used on the dpkg command line. Wording from Colin Watson. Closes #504880. --- diff --git a/policy.sgml b/policy.sgml index 9b9ee4c..f5c6818 100644 --- a/policy.sgml +++ b/policy.sgml @@ -1040,8 +1040,8 @@

- Sometimes, a package requires another package to be installed - and configured before it can be installed. In this + Sometimes, a package requires another package to be unpacked + and configured before it can be unpacked. In this case, you must specify a Pre-Depends entry for the package.

@@ -3462,7 +3462,7 @@ Package: libc6

Broadly speaking the preinst is called before - (a particular version of) a package is installed, and the + (a particular version of) a package is unpacked, and the postinst afterwards; the prerm before (a version of) a package is removed and the postrm afterwards. @@ -3841,7 +3841,7 @@ Package: libc6 behavior which, though deterministic, is hard for the system administrator to understand. It can easily lead to "missing" programs if, for example, a package - is installed which overwrites a file from another + is unpacked which overwrites a file from another package, and is then removed again. Part of the problem is due to what is arguably a bug in dpkg. @@ -3977,7 +3977,7 @@ Package: libc6 If there was a conflicting package we go and do the removal actions (described below), starting with the removal of the conflicting package's files (any that - are also in the package being installed have already + are also in the package being unpacked have already been removed from the conflicting package's file list, and so do not get removed now). @@ -4285,8 +4285,8 @@ Build-Depends: foo [!i386] | bar [!amd64] removal order honoring the dependency order can't be established, dependency loops are broken at some point (based on rules below), and some packages may not be able to - rely on their dependencies being present when being - installed or removed, depending on which side of the break + rely on their dependencies being unpacked when being + unpacked or removed, depending on which side of the break of the circular dependency loop they happen to be on. If one of the packages in the loop has no postinst script, then the cycle will be broken at that package, so as to ensure that @@ -4435,7 +4435,7 @@ Build-Depends: foo [!i386] | bar [!amd64]

When one binary package declares that it breaks another, dpkg will refuse to allow the package which - declares Breaks be installed unless the broken + declares Breaks be unpacked unless the broken package is deconfigured first, and it will refuse to allow the broken package to be reconfigured.

@@ -4476,13 +4476,13 @@ Build-Depends: foo [!i386] | bar [!amd64]

When one binary package declares a conflict with another using a Conflicts field, dpkg will - refuse to allow them to be installed on the system at the + refuse to allow them to be unpacked on the system at the same time.

- If one package is to be installed, the other must be removed - first - if the package being installed is marked as + If one package is to be unpacked, the other must be removed + first - if the package being unpacked is marked as replacing (see ) the one on the system, or the one on the system is marked as deselected, or both packages are marked Essential, then @@ -4677,7 +4677,7 @@ Provides: mail-transport-agent Conflicts: mail-transport-agent Replaces: mail-transport-agent - ensuring that only one MTA can be installed at any one + ensuring that only one MTA can be unpacked at any one time. @@ -4909,7 +4909,7 @@ Replaces: mail-transport-agent

During install or upgrade, the preinst is called before - the new files are installed, so calling "ldconfig" is + the new files are unpacked, so calling "ldconfig" is pointless. The preinst of an existing package can also be called if an upgrade fails. However, this happens during the critical time when a shared libs may exist on-disk @@ -5045,7 +5045,7 @@ Replaces: mail-transport-agent ) to ensure that the user only installs one development version at a time (as different development versions are likely to have the same header files in them, which would cause a - filename clash if both were installed). + filename clash if both were unpacked).

@@ -9305,7 +9305,7 @@ install-info --quiet --remove /usr/share/info/foobar.info

The DEBIAN directory will not appear in the file system archive of the package, and so won't be installed - by dpkg when the package is installed. + by dpkg when the package is unpacked.