| 1 |
On Wed, 2006-01-04 at 09:13 -0800, Robin H. Johnson wrote: |
| 2 |
> On Wed, Jan 04, 2006 at 05:45:22PM +0100, Patrick Lauer wrote: |
| 3 |
> > Now I'm wondering - is there a sane way of handling this that doesn't |
| 4 |
> > forcefully remove python 2.4? |
| 5 |
> > e.g. could python modules be installed to multiple python versions? How |
| 6 |
> > do others (ruby, perl, ...) handle it? For the moment I've "solved" that |
| 7 |
> > by package.masking python 2.4, unmerging it and rebuilding all Python |
| 8 |
> > modules - less than optimal ... |
| 9 |
> See dev-python/validation-1.2.3 for another solution. |
| 10 |
> It installs itself for all versions of Python that are on the system. |
| 11 |
I don't fully understand the magic how it finds all Python versions, but can this be applied to other packages? |
| 12 |
Are there reasons for not doing this (besides increasing build time)? |
| 13 |
|
| 14 |
Also - how does portage react to "multi-installing" packages? |
| 15 |
|
| 16 |
|
| 17 |
Thanks, |
| 18 |
|
| 19 |
Patrick |
| 20 |
-- |
| 21 |
Stand still, and let the rest of the universe move |
Archives