Ian Jackson writes ("auto-deconfigure is not transitive"):
> Package: dpkg
> Version: 1.13.22
>
> If
> A -Conflicts/Replaces-> B <-Depends- C <-Depends- D
>
> and you start with B,C,D installed, then installing A automatically
> removes B (which is correct) and deconfigures C (which is correct) but
> fails to deconfigure D (which is not correct).
I think I may be confused here.
We already have the situation that if
B <-Depends- C
and you upgrade B, then B goes through half-installed and unpacked
without any (dpkg-recorded or -implemented) effect on C.
This counterexample shows that we don't
B <-Depends- C && installed(C) => installed(B)
as an invariant in general, and I think it needn't apply in this case
either. Deconfiguring due to --auto-deconfigure is less potentially
damaging than installation of a new package.
Ian.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
