+debian-policy (3.1.1.2) unstable; urgency=low
+
+ * Correct missing </chapt> in packaging.sgml (closes: #51091)
+ * Correct typo in policy 2.3.5 (closes: #52225)
+
+ -- Julian Gilbey <jdg@debian.org> Mon, 20 Dec 1999 20:39:57 +0000
+
debian-policy (3.1.1.1) unstable; urgency=low
* Correction to typo in packaging manual, section 6.2.
+++ /dev/null
-#!/bin/sh
-# -*- Mode: Sh -*-
-# postinst ---
-# Author : Manoj Srivastava ( srivasta@tiamat.datasync.com )
-# Created On : Thu Oct 29 15:23:36 1998
-# Created On Node : tiamat.datasync.com
-# Last Modified By : Manoj Srivastava
-# Last Modified On : Thu Oct 29 15:28:24 1998
-# Last Machine Used: tiamat.datasync.com
-# Update Count : 3
-# Status : Unknown, Use with caution!
-# HISTORY :
-# Description :
-#
-#
-
-
-# Abort if any command returns an error value
-set -e
-
-
-# This script is called as the last step of the installation of the
-# package. All the package's files are in place, dpkg has already done
-# its automatic conffile handling, and all the packages we depend of
-# are already fully installed and configured.
-
-
-case "$1" in
- configure)
- # Configure this package. If the package must prompt the user for
- # information, do it here.
- :
-
- if [ -x /usr/sbin/install-docs ]; then
- /usr/sbin/install-docs -i /usr/share/doc-base/debian-policy
- fi
-
- # There are three sub-cases:
- if test "${2+set}" != set; then
- # We're being installed by an ancient dpkg which doesn't remember
- # which version was most recently configured, or even whether
- # there is a most recently configured version.
- :
-
- elif test -z "$2" -o "$2" = "<unknown>"; then
- # The package has not ever been configured on this system, or was
- # purged since it was last configured.
- :
-
- else
- # Version $2 is the most recently configured version of this
- # package.
- :
-
- fi ;;
- abort-upgrade)
- # Back out of an attempt to upgrade this package FROM THIS VERSION
- # to version $2. Undo the effects of "prerm upgrade $2".
- :
-
- ;;
- abort-remove)
- if test "$2" != in-favour; then
- echo "$0: undocumented call to \`postinst $*'" 1>&2
- exit 0
- fi
- # Back out of an attempt to remove this package, which was due to
- # a conflict with package $3 (version $4). Undo the effects of
- # "prerm remove in-favour $3 $4".
- :
-
- ;;
- abort-deconfigure)
- if test "$2" != in-favour -o "$5" != removing; then
- echo "$0: undocumented call to \`postinst $*'" 1>&2
- exit 0
- fi
- # Back out of an attempt to deconfigure this package, which was
- # due to package $6 (version $7) which we depend on being removed
- # to make way for package $3 (version $4). Undo the effects of
- # "prerm deconfigure in-favour $3 $4 removing $6 $7".
- :
-
- ;;
- *) echo "$0: didn't understand being called with \`$1'" 1>&2
- exit 0;;
-esac
-
-exit 0
+++ /dev/null
-#!/bin/sh
-# -*- Mode: Sh -*-
-# prerm ---
-# Author : Manoj Srivastava ( srivasta@tiamat.datasync.com )
-# Created On : Thu Oct 29 15:31:03 1998
-# Created On Node : tiamat.datasync.com
-# Last Modified By : Manoj Srivastava
-# Last Modified On : Thu Oct 29 15:33:43 1998
-# Last Machine Used: tiamat.datasync.com
-# Update Count : 1
-# Status : Unknown, Use with caution!
-# HISTORY :
-# Description :
-#
-#
-
-# Abort if any command returns an error value
-set -e
-
-# This script is called as the first step in removing the package from
-# the system. This includes cases where the user explicitly asked for
-# the package to be removed, upgrade, automatic removal due to conflicts,
-# and deconfiguration due to temporary removal of a depended-on package.
-
-case "$1" in
- remove)
- # This package about to be removed.
- :
-
- # There are two sub-cases:
- if test "${2+set}" = set; then
- if test "$2" != in-favour; then
- echo "$0: undocumented call to \`prerm $*'" 1>&2
- exit 0
- fi
- # We are being removed because of a conflict with package $3
- # (version $4), which is now being installed.
- :
-
- else
- # The package is being removed in its own right.
- :
-
- fi ;;
- deconfigure)
- if test "$2" != in-favour -o "$5" != removing; then
- echo "$0: undocumented call to \`prerm $*'" 1>&2
- exit 0
- fi
- # Package $6 (version $7) which we depend on is being removed due
- # to a conflict with package $3 (version $4), and this package is
- # being deconfigured until $6 can be reinstalled.
- :
-
- ;;
- upgrade)
- # Prepare to upgrade FROM THIS VERSION of this package to version $2.
- :
-
- ;;
- failed-upgrade)
- # Prepare to upgrade from version $2 of this package TO THIS VERSION.
- # This is only used if the old version's prerm couldn't handle it,
- # and returned non-zero. (Fix old prerm bugs here.)
- :
-
- ;;
- *) echo "$0: didn't understand being called with \`$1'" 1>&2
- exit 0;;
-esac
-
-if [ -x /usr/sbin/install-docs ]; then
- /usr/sbin/install-docs -r debian-policy
-fi
-
-exit 0
</footnote>
</p>
</sect>
-
+ </chapt>
+
<chapt id="sourcepkg">
<heading>Source packages</heading>
<p>
If you need to compare version numbers in a script, you may use
<tt>dpkg --compare-versions ...</tt>. Type <tt>dpkg
- --help</tt> --> --for details on arguments.
+ --help</tt> for details on arguments.
</p>
<sect>
<footnote>
<p>
Part of the problem is due to what is arguably a
- bug in <prgn>dpkg</prgn> .
+ bug in <prgn>dpkg</prgn>.
</p>
</footnote>
</p>
<sect><heading>Relationships between source and binary packages -
<tt>Build-Depends</tt>, <tt>Build-Depends-Indep</tt>,
<tt>Build-Conflicts</tt>, <tt>Build-Conflicts-Indep</tt>
- </heading>
+ </heading>
<p>
A source package may declare a dependency or a conflict on a
when one of the targets in <tt>debian/rules</tt> that the
particular field applies to is invoked.
- <taglist>
- <tag><tt>Build-Depends</tt>, <tt>Build-Conflicts</tt></tag>
- <item>
- <p>
- The <tt>Build-Depends</tt> and <tt>Build-Conflicts</tt> fields apply
- to the targets
- <tt>build</tt>, <tt>binary</tt>, <tt>binary-arch</tt>
- and <tt>binary-indep</tt>.
- </p>
- </item>
- <tag><tt>Build-Depends-Indep</tt>, <tt>Build-Conflicts-Indep</tt></tag>
- <item>
- <p>
- The <tt>Build-Depends-Indep</tt> and
- <tt>Build-Conflicts-Indep</tt> fields apply to the
- targets <tt>binary</tt> and <tt>binary-indep</tt>.
- </p>
- </item>
- </taglist>
+ <taglist>
+ <tag><tt>Build-Depends</tt>, <tt>Build-Conflicts</tt></tag>
+ <item>
+ The <tt>Build-Depends</tt> and
+ <tt>Build-Conflicts</tt> fields apply to the targets
+ <tt>build</tt>, <tt>binary</tt>, <tt>binary-arch</tt>
+ and <tt>binary-indep</tt>.
+ </p>
+ </item>
+ <tag><tt>Build-Depends-Indep</tt>, <tt>Build-Conflicts-Indep</tt></tag>
+ <item>
+ The <tt>Build-Depends-Indep</tt> and
+ <tt>Build-Conflicts-Indep</tt> fields apply to the
+ targets <tt>binary</tt> and <tt>binary-indep</tt>.
+ </p>
+ </item>
+ </taglist>
- </p>
+ </p>
- </sect>
+ </sect>
+ </chapt>
- </chapt>
<chapt id="conffiles"><heading>Configuration file handling
</heading>
</book>
</debiandoc>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
<p>
Sometimes, there are several packages doing more-or-less
the same job. In this case, it's useful to define a
- <em>virtual package</em> who's name describes the function
+ <em>virtual package</em> whose name describes the function
the packages have. (The virtual packages just exist
logically, not physically--that's why they are called
<em>virtual</em>.) The packages with this particular
projects / debian / debian-policy.git / commitdiff