On Wed, Jan 04, 2006 at 08:59:04PM +0100, Patrick Lauer wrote: > > 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? It can and it is. Can't recall offhand which, but the basic premise is N copies of the source (worst case, only 1 copy if the build system is written correctly), each compiled slightly differently (eg for different Python versions).
> Are there reasons for not doing this (besides increasing build time)? None that I am aware of. Probably best to avoid doing this on any package with a long build time, or where useless stuff is built multiple times (eg build N binaries, build 1 set of docs only). > Also - how does portage react to "multi-installing" packages? For portage's point of view, the package is installed once. It's not strictly binpkg safe, but the python packages aren't either. (Have just python2.N on a system, make a binpkg of a python mod, upgrade python, remove old python, and now your binpkg is useless). -- Robin Hugh Johnson E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
pgphAaOmzscIM.pgp
Description: PGP signature
