On So, 07 Jun 2009, Josselin Mouette wrote:
> Le vendredi 05 juin 2009 à 21:15 +0200, Frank Küster a écrit :
> > texlive-base's postrm, upon REMOVE, uses a command from tex-common, on
> > which it already DEPENDS. This is allowed by policy.
>
> I’m not sure about the policy, but I’m certain that with the current
> dpkg version this will fail miserably in many cases. The only packages
Many cases? I disagree. Only in the case that someone removes a package
with --force, right? All other variants should be handled (hopefully!).
> that are guaranteed to be available in the postrm are the essential
> packages.
Not according to the policy.
> > It seems it is a bug of policy, or dpkg.
>
> Fixing the policy is probably easier than fixing dpkg…
Agreed on that, but OTOH, that is *really* a problematic system, because
we might leave things hanging around in a completely malconfigured way,
and reinstallations do not allow to overwrite stuff (maybe). I don't
have a szenario at hand, but I guess that changing policy in this
respect is not a piece of cake, either.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <prein...@logic.at> Vienna University of Technology
Debian Developer <prein...@debian.org> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
AYNHO (vb.)
Of waiters, never to have a pen.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
