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