Hi all, I recently ran into an interesting problem:
One app I have seems to trigger a bug in Python 2.4, so I want to use it with Python 2.3 But, as it imports a few python modules I can't use it - the modules only get installed to the most recent Python version. From a portage dependency p.o.v it is satisfied - $program needs Python 2.3 and (among others) PyCrypto, but PyCrypto is only available in Python 2.4 and fails to import in 2.3 Now I'm wondering - is there a sane way of handling this that doesn't forcefully remove python 2.4? e.g. could python modules be installed to multiple python versions? How do others (ruby, perl, ...) handle it? For the moment I've "solved" that by package.masking python 2.4, unmerging it and rebuilding all Python modules - less than optimal ... Thanks, Patrick -- Stand still, and let the rest of the universe move
signature.asc
Description: This is a digitally signed message part