Re: Full install/removal/upgrade test results available
On Wed, Dec 29, 2010 at 01:52:13PM +0100, Josselin Mouette wrote:
> Le mercredi 29 décembre 2010 à 12:50 +0000, Ian Jackson a écrit :
> > If so, that's a bug in python-xpcom. Any package which registers a
> > hook with another package must be prepared for its hook to be run even
> > when the registering package is not configured. If this is a problem,
> > arrangements should be made to arrange that the hook is a no-op when
> > in these circumstances and/or that it is run later when the
> > registering package is properly working.
> >
> > For example, the hook could be registered only in python-xpcom's
> > postinst (and deregistered in its preinst).
>
> This is what I have already proposed to Mike on IRC: moving
> libpyloader.so to a different directory and setting it as a symlink in
> python-xpcom.postinst.
Which would also mean firing dpkg-trigger in python-xpcom.postinst, too.
This all looks like overcomplication to circumvent an imho design flaw in
python packages. Unfortunately, except if I drop python-support use
entirely (which could even mean going against the python policy, but I
don't remember the details of it wrt modules location), there's nothing
else I can do.
Mike
Reply to: