Hi Alexandre & others, On Mon, Sep 7, 2009 at 10:21, Alexandre Fayolle <alexandre.fayo...@logilab.fr> wrote: > The problem I can see with removing blindly from the postinst is that > potentially you're going to delete files belonging to other packages (e.g. > older packages installed from Logilab's Debian repositories).
They won't work anyway: they have to be ported to python-support too. This because if /usr/lib/python*/site-packages/logilab/ is left there, new packages won't work, but neither the old, since they would use the new one (migrated to pysupport), but they're not functional, so we closed the cycle :( > Could the following work: > > logilab-common postinst removes /usr/lib/python*/site- > packages/logilab/__init__.py*, and issues a warning if there are other stuff > in > the directory : this will stop packages installed under that tree from working > without deleting the files themselves (enabling the administrator to find out > what's broken with that installation). For what said above, I have implemented the solution of "brutally" removing /usr/lib/python*/site-packages/logilab/ in loglab-common (since it's the commno (base) ground for all the other logilab packages), adding conflicts with the older versions of logilab-* pkgs and bumping the dependencies on logilab-* to the most recent version of logilab-common. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
