Le mercredi 29 décembre 2010 à 14:19 +0100, Mike Hommey a écrit : > xulrunner has a file trigger for components in > /usr/lib/xulrunner-1.9.1/components, so that it registers them in > compreg.dat and xpti.dat. This means it has to load the components to > get their registration information. But the components python-xpcom adds > need the python modules to be registered to work, which means xulrunner > component registration need to happen after python-xpcom's modules are > available, which usually only happens after python-support's trigger, > but in python-xpcom case, it's forced to run during its postinst, which > is unfortunately still too late.
Note that in the python-xpcom case, it is useless to force update-python-modules -p in the postinst. The symlinks are installed by the postinst and are sufficient for anything that needs the modules. The trigger is here for byte-compilation. Cheers, -- .''`. : :' : “You would need to ask a lawyer if you don't know `. `' that a handshake of course makes a valid contract.” `- -- J???rg Schilling -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1293639833.27024.39.ca...@meh
