From a858ac70eec8347fb3189e835846a6736b44ef7b Mon Sep 17 00:00:00 2001 From: Manoj Srivastava Date: Thu, 16 Jun 2005 05:34:14 +0000 Subject: [PATCH] Added example for why one may call ldconfig anywhere in the Author: srivasta Date: 2002/11/13 06:05:25 Added example for why one may call ldconfig anywhere in the postsint. closes: Bug#120585 git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-148 --- debian/changelog | 7 +++++++ policy.sgml | 29 ++++++++++++++++------------- 2 files changed, 23 insertions(+), 13 deletions(-) diff --git a/debian/changelog b/debian/changelog index aed40f3..b222419 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +debian-policy (3.5.8.0) unstable; urgency=low + + * Added example for why one may call ldconfig anywhere in the + postsint. closes: Bug#120585 + + -- Manoj Srivastava Wed, 13 Nov 2002 00:04:50 -0600 + debian-policy (3.5.7.1) unstable; urgency=low * Fix the debconf spec to (postinst -> postrm) closes: Bug#129375, Bug#160839 diff --git a/policy.sgml b/policy.sgml index e309097..ccf5654 100644 --- a/policy.sgml +++ b/policy.sgml @@ -3790,19 +3790,22 @@ Replaces: mail-transport-agent forbidden by current policy to call "ldconfig" at this time. When a package is installed or upgraded, "postinst configure" runs after the new files are safely on-disk. - 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 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. The postrm - can be called at several other times. At the time of - "postrm purge", "postrm abort-install", or "postrm + Since it is perfectly safe to invoke ldconfig + unconditionally in a postinst, it is OK for a package to + simply put ldconfig in its postinst without checking the + 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 + 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. + 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 shared lib files are not on-disk. However, when "postrm" is invoked with arguments "upgrade", "failed-upgrade", or -- 2.39.5