On Wed, 2006-01-04 at 09:13 -0800, Robin H. Johnson wrote: > On Wed, Jan 04, 2006 at 05:45:22PM +0100, Patrick Lauer wrote: > > 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 ... > See dev-python/validation-1.2.3 for another solution. > It installs itself for all versions of Python that are on the system. I don't fully understand the magic how it finds all Python versions, but can this be applied to other packages? Are there reasons for not doing this (besides increasing build time)?
Also - how does portage react to "multi-installing" packages? Thanks, Patrick -- Stand still, and let the rest of the universe move
signature.asc
Description: This is a digitally signed message part
