| 1 |
On Wed, Jan 04, 2006 at 08:59:04PM +0100, Patrick Lauer wrote: |
| 2 |
> > It installs itself for all versions of Python that are on the |
| 3 |
> > system. |
| 4 |
> I don't fully understand the magic how it finds all Python versions, |
| 5 |
> but can this be applied to other packages? |
| 6 |
It can and it is. Can't recall offhand which, but the basic premise is |
| 7 |
N copies of the source (worst case, only 1 copy if the build system is |
| 8 |
written correctly), each compiled slightly differently (eg for |
| 9 |
different Python versions). |
| 10 |
|
| 11 |
> Are there reasons for not doing this (besides increasing build time)? |
| 12 |
None that I am aware of. Probably best to avoid doing this on any |
| 13 |
package with a long build time, or where useless stuff is built |
| 14 |
multiple times (eg build N binaries, build 1 set of docs only). |
| 15 |
|
| 16 |
> Also - how does portage react to "multi-installing" packages? |
| 17 |
For portage's point of view, the package is installed once. |
| 18 |
It's not strictly binpkg safe, but the python packages aren't either. |
| 19 |
(Have just python2.N on a system, make a binpkg of a python mod, |
| 20 |
upgrade python, remove old python, and now your binpkg is useless). |
| 21 |
|
| 22 |
-- |
| 23 |
Robin Hugh Johnson |
| 24 |
E-Mail : robbat2@g.o |
| 25 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives