| 1 |
On Sat, 22 Sep 2012 21:46:02 -0300 |
| 2 |
Alexis Ballier <aballier@g.o> wrote: |
| 3 |
|
| 4 |
> On Sat, 22 Sep 2012 23:24:46 +0200 |
| 5 |
> Michał Górny <mgorny@g.o> wrote: |
| 6 |
> |
| 7 |
> > It is a simple eclass using autotools out-of-source builds to build |
| 8 |
> > packages for multiple ABIs when multilib is supported. |
| 9 |
> > |
| 10 |
> |
| 11 |
> to some extent, can't you do the same by unpacking twice to different |
| 12 |
> $S and calling src_prepare/compile/install instead of their |
| 13 |
> autotools-utils counterpart with tweaked $S so that it works with |
| 14 |
> almost every ebuild ? |
| 15 |
|
| 16 |
That would make this solution inefficient. The good solutions should |
| 17 |
not be made ugly to support corner cases. |
| 18 |
|
| 19 |
> -- this really starts to resemble multilib portage :) |
| 20 |
|
| 21 |
I've said already that multilib is a thing which could be done by |
| 22 |
eclasses and doesn't need making PM scary. And Tommy says that |
| 23 |
multilib-portage handles packages having IUSE=multilib fine. |
| 24 |
|
| 25 |
-- |
| 26 |
Best regards, |
| 27 |
Michał Górny |
Archives