| 1 |
On Monday, June 27, 2011 09:43:05 Dirkjan Ochtman wrote: |
| 2 |
> On Mon, Jun 27, 2011 at 15:08, Fabian Groffen wrote: |
| 3 |
> > It would be nice when a similar technique could be implemented only |
| 4 |
> > once, in a consistent way. In a way, multilib-portage can be considered |
| 5 |
> > equal to one of the objectives of the python (and ruby) eclass: |
| 6 |
> > multiple times compiling and installing for different ABIs. |
| 7 |
> |
| 8 |
> Yeah, but it'd be nice not to have to compile subversion three times |
| 9 |
> just because we want the python bindings installed in three different |
| 10 |
> Python environments. |
| 11 |
|
| 12 |
it'd be nice to not build glibc multiple times for diff multilibs, but it |
| 13 |
simply isnt possible. either you want multilib support (or in this case |
| 14 |
multi-python version support), or you dont. if this feature is something like |
| 15 |
(and it sounds like it is), then this is simply something that is accepted. |
| 16 |
|
| 17 |
if you dont want multiple builds on your system, then dont install multiple |
| 18 |
versions of python. |
| 19 |
-mike |
Archives