On Tue, 2006-06-13 at 22:05 +0200, Mike Hommey wrote: > On Tue, Jun 13, 2006 at 09:55:08PM +0200, Raphael Hertzog <hertzog@debian.org> wrote: > > When you install some python extensions (.so), it is common that they come with > > associated .py files (modules). Those .py files usually are the same in > > /usr/lib/python2.3 and /usr/lib/python2.4, that's why python-central will > > keep only one copy of them in /usr/share/pycentral and symlink them back into > > /usr/lib/python2.[34]/ ... > > > > However if the .py installed in /usr/lib/python2.3 is different from the > > one installed in /usr/lib/python2.4, then you can't share it between both > > versions (and you need the DH_PYCENTRAL="nomove" variable). That what's I > > meant. Feel free to fix the wording in the wiki if you have a better way > > to express it. > > Okay, it sounds clearer said like that. Stupid question: why doesn't > pycentral autodetect if files are different or not ? I don't actually > see a reason why DH_PYCENTRAL need to be set... > > > > PS: Anyways, there's one package you didn't list because it's in NEW, > > > which WON'T be merged as required by the new policy: python2.x-xpcom, > > > provided by xulrunner. > > > The reason is simple: different installations for different python > > > versions CAN'T coexist without breaking each other. > > > > OK, then indicate "current" in XS-Python-Version and support only the > > current version in python-xpcom (make sure to generate the provides > > field). > > What about people who want to use pyxpcom with modules that aren't > available with the current python ? But a user couldn't install more than one such module at a time, since the packages are mutually exclusive. It seems far better to me to just force everyone to use one version and avoid the issue. Or, fix pyxpcom, which sounds horribly broken. -- Joe Wreschnig <piman@sacredchao.net>
Attachment:
signature.asc
Description: This is a digitally signed message part