Le lundi 24 avril 2006 à 18:11 +0100, Colin Watson a écrit : > The postinst fragments installed by dh_python compile everything under > /usr/lib/pythonX.Y/site-packages, so if you're installing several > python-using packages at once it's entirely possible for a package to be > only unpacked yet still have .pyc and .pyo files created for it by a > postinst of one of the other packages being installed in the same run.
[snip] > I haven't tested this, but I believe that the easiest fix is to move > dh_python's prerm fragment to postrm, and guard it with a check that $1 > is remove. Unfortunately this isn't possible, as the prerm script uses dpkg to obtain the list of files the package provides, and it isn't available at postrm time. Furthermore, the case where .py files are removed from a release to another would have to be handled by hand. I think this can be fixed by using python-support, but it still needs a bit of work before being usable by dh_python. Regards, -- .''`. Josselin Mouette /\./\ : :' : [EMAIL PROTECTED] `. `' [EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
signature.asc
Description: Ceci est une partie de message numériquement signée
