Le jeudi 09 avril 2009 à 01:43 +0200, Bernd Zeimetz a écrit : > While the idea of having .noinit is good to work around braindead upstreams, > it is implemented badly unfortunately. > > Adding some debug code to update-python-modules shows me, that it looks > in /usr/lib/pymodules/python*/... for the .noinit files: > > checking for .noinit: /usr/lib/pymodules/python2.4/PyQt4/uic/widget-plugins > > create namespace > /usr/lib/pymodules/python2.4/PyQt4/uic/widget-plugins/__init__.py > > This is is nto future-proof, as you'd have to install .noinit files in the > pymodules directories for all new Python versions. > > I'd expect to drop the .noinit file for modules in /usr/share/pyshared.
It works as expected if the .noinit is listed
in /usr/share/python-support/foo.public, but I understand now this is a
bad idea, because you will generally create it later on
in /usr/share/pyshared.
I can think of two workarounds:
* create the .noinit
in /usr/share/python-support/foo/PyQt4/uic/widget-plugins/.noinit, it
should work if you do that before dh_pysupport (but that’s fugly).
* create it in /usr/lib/pythonX.Y/site-packages/... before
dh_pysupport
As for the solution, I’d like to avoid looking in /usr/share/pyshared
because anyone can write here, and it’s not guaranteed that the file is
needed for this particular Python version. Furthermore, it would
completely break the current two-step logic.
Maybe adding a parameter so that you can do:
dh_pysupport --ignore-init foo/PyQt4/uic/widget-plugins
would do the trick ?
--
.''`. Debian 5.0 "Lenny" has been released!
: :' :
`. `' Last night, Darth Vader came down from planet Vulcan and told
`- me that if you don't install Lenny, he'd melt your brain.
signature.asc
Description: Ceci est une partie de message numériquement signée
