in the footnote related to ldconfig, split paragraphs per each maintainer script...

Author: joy
Date: 2002/11/13 16:40:10
in the footnote related to ldconfig, split paragraphs per each maintainer script, and rephrased an incoherent sentence about the postrm

git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-149

diff --git a/policy.sgml b/policy.sgml
index ccf5654fda75b9c753875dea6f3156fc3e197e43..583cac08f628e4d0c8ab04b6015a5d4706d844cd 100644 (file)
--- a/policy.sgml
+++ b/policy.sgml
@@ -3788,7 +3788,9 @@ Replaces: mail-transport-agent
            the critical time when a shared libs may exist on-disk
            under a temporary name.  Thus, it is dangerous and
            forbidden by current policy to call "ldconfig" at this
-           time.  When a package is installed or upgraded, "postinst
+           time.
+          </p>
+          <p>When a package is installed or upgraded, "postinst
            configure" runs after the new files are safely on-disk.
            Since it is perfectly safe to invoke ldconfig
            unconditionally in a postinst, it is OK for a package to
@@ -3796,14 +3798,18 @@ Replaces: mail-transport-agent
            argument.  The postinst can also be called to recover from
            a failed upgrade.  This happens before any new files are
            unpacked, so there is no reason to call "ldconfig" at this
-           point.  For a package that is being removed, prerm is
+           point.
+          </p>
+          <p>For a package that is being removed, prerm is
            called with all the files intact, so calling ldconfig is
            useless.  The other calls to "prerm" happen in the case of
            upgrade at a time when all the files of the old package
-           are on-disk, so again calling "ldconfig" is pointless. If
-           An installed shared lib has been removed from the system
-           just before "postrm remove" is run.  This is the proper
-           time to call "ldconfig" to notify the system of that fact.
+           are on-disk, so again calling "ldconfig" is pointless.
+          </p>
+          <p>postrm, on the other hand, is called with the "remove"
+            argument just after the files are removed, so this is the
+            proper time to call "ldconfig" to notify the system of the
+            fact shared libraries from the package are removed.
            The postrm can be called at several other times.  At the
            time of "postrm purge", "postrm abort-install", or "postrm
            abort-upgrade", calling "ldconfig" is useless because the