Op di, 16-05-2006 te 22:21 +0300, schreef Antti-Juhani Kaijanaho:
> Arjan Oosting wrote:
> > To solve this we either Pre-Depends on ghc6
>
> No, that is the wrong solution. Pre-Depends are mainly used in
> Essential: yes packages; it is wrong in almost all other cases.
>
> This bug seems strange, though. Since libghc6-c2hs-dev depends on ghc6,
> the latter should be configured when libghc6-c2hs-dev is being
> (de)configured. I suspect that libghc6-c2hs-dev was not the only
> package involved in the upgrade, yet the bug logs don't show the whole
> upgrade; that we are not seeing the whole picture here.
Indeed you are right and I am wrong :)
From policy:
Depends
This declares an absolute dependency. A package will not be
configured unless all of the packages listed in its Depends
field have been correctly configured.
The Depends field should be used if the depended-on package is
required for the depending package to provide a significant
amount of functionality.
The Depends field should also be used if the postinst, prerm or
postrm scripts require the package to be present in order to
run. Note, however, that the postrm cannot rely on any
non-essential packages to be present during the purge phase.
So indeed the Depends relationship is right and it should NOT be a
pre-depends. Sorry for the noise.
Greetings Arjan
Attachment:
signature.asc
Description: Dit berichtdeel is digitaal ondertekend