1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Patrick Lauer wrote: |
5 |
| Hi all, |
6 |
| |
7 |
| I recently ran into an interesting problem: |
8 |
| |
9 |
| One app I have seems to trigger a bug in Python 2.4, so I want to use it |
10 |
| with Python 2.3 |
11 |
| But, as it imports a few python modules I can't use it - the modules |
12 |
| only get installed to the most recent Python version. |
13 |
| |
14 |
| From a portage dependency p.o.v it is satisfied - $program needs Python |
15 |
| 2.3 and (among others) PyCrypto, but PyCrypto is only available in |
16 |
| Python 2.4 and fails to import in 2.3 |
17 |
| |
18 |
| Now I'm wondering - is there a sane way of handling this that doesn't |
19 |
| forcefully remove python 2.4? |
20 |
| e.g. could python modules be installed to multiple python versions? How |
21 |
| do others (ruby, perl, ...) handle it? For the moment I've "solved" that |
22 |
| by package.masking python 2.4, unmerging it and rebuilding all Python |
23 |
| modules - less than optimal ... |
24 |
|
25 |
Many programs have configure options for where the python module |
26 |
directory is, or which python version they're using. If not, move the |
27 |
files around manually in src_install(). |
28 |
|
29 |
sci-chemistry/sparky installs for python 2.3 only. |
30 |
|
31 |
Thanks, |
32 |
Donnie |
33 |
-----BEGIN PGP SIGNATURE----- |
34 |
Version: GnuPG v1.4.2 (GNU/Linux) |
35 |
|
36 |
iD8DBQFDvAAKXVaO67S1rtsRApdSAJ4kwf5XROsGKrH7dSl0kjU/HfkguQCdHBUT |
37 |
Kkd7jOjHz+9Q9HcfpQBr+yM= |
38 |
=csaK |
39 |
-----END PGP SIGNATURE----- |
40 |
-- |
41 |
gentoo-dev@g.o mailing list |