| 1 |
On Tue, 2 Apr 2013 23:42:42 +0200 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> Currently, the multilib-build eclass uses abi_* constants only for USE |
| 5 |
> flags and only ${ABI} is exported to the function. This is bad since it |
| 6 |
> basically requires a reverse mapping of ABI->abi_* values, often |
| 7 |
> inlined as ${ABI} checks. |
| 8 |
|
| 9 |
Due to the multilib-portage conflicts pointed out by Tommy, and other |
| 10 |
potential issues resulting from spreading the use of abi_* constants |
| 11 |
over the tree, I have decided to withdraw these patches for now. |
| 12 |
|
| 13 |
They may be re-considered in the future when multilib-portage will |
| 14 |
respect and use the eclass, or when a better and less conflicting |
| 15 |
method is found. |
| 16 |
|
| 17 |
-- |
| 18 |
Best regards, |
| 19 |
Michał Górny |
Archives