Bug#504880: Disambiguate "installed" for packages
Hi,
On Sun, 01 Feb 2009, Russ Allbery wrote:
> There isn't any further discussion of this in the bug log, and I don't
> think there was a reply outside of the bug log. I agree with Colin that
> simply changing present to unpacked is potentially confusing, but I would
> like to clarify the case for prerm upgrade, and I think it might be worth
> drawing the distinction here between what one can normally expect
> (configured) and what one may get given circular dependencies.
The case of circular dependencies is covered a few paragrapth above
the explanation of Depends. I added a small note that tells to check back
but that's all. I detailed the case of each script however.
> Does anyone have a specific wording proposal here? I think that's all
> that's needed before resolving this bug.
Please find a proposed patch in attachment. Feel free to reword/improve if needed.
Cheers,
--
Raphaël Hertzog
Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/
diff --git a/policy.sgml b/policy.sgml
index f5c6818..8727be1 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -4323,10 +4323,17 @@ Build-Depends: foo [!i386] | bar [!amd64]
The <tt>Depends</tt> field should also be used if the
<prgn>postinst</prgn>, <prgn>prerm</prgn> or
<prgn>postrm</prgn> scripts require the package to be
- present in order to run. Note, however, that the
- <prgn>postrm</prgn> cannot rely on any non-essential
- packages to be present during the <tt>purge</tt>
- phase.
+ present in order to run (if both packages are involved in a
+ dependency loop, this might not work as expected, see the
+ explanation a few paragraphs back). In the case of
+ <prgn>postinst</prgn> and <prgn>postrm</prgn>, the
+ depended-on packages will be unpacked and configured.
+ Note, however, that the <prgn>postrm</prgn> cannot rely on
+ any non-essential packages to be present during the
+ <tt>purge</tt> phase. In the case of <prgn>prerm</prgn>,
+ the depended-on package will at least be unpacked (it might
+ be configured too, but you can't rely on it unless you use
+ <tt>Pre-Depends</tt>).
</item>
<tag><tt>Recommends</tt></tag>
Reply to: