1 |
On Wed, 03 Apr 2013 11:40:31 +0200 |
2 |
Thomas Sachau <tommy@g.o> wrote: |
3 |
|
4 |
> Michał Górny schrieb: |
5 |
> > The first patch changes the eclass logic. The abi_* values, with 'abi_' |
6 |
> > prefix stripped, are called MULTILIB_ABI now. They are used to run |
7 |
> > the 'foreach' functions, and now are set in the called functions along |
8 |
> > with ABI. |
9 |
> > |
10 |
> > [...] |
11 |
> > |
12 |
> > Additionally, the 'default' fallback no longer calls |
13 |
> > multilib_toolchain_setup. This should improve compatibility with |
14 |
> > multilib-portage and *maybe* cross-compiling. |
15 |
> |
16 |
> You know, that multilib-portage does use MULTILIB_ABI as USE-expanded |
17 |
> variable? Using exactly the same in the eclass will call for collision |
18 |
> issues. |
19 |
|
20 |
Ok, I see one more issue. Whenever ebuilds start checking |
21 |
MULTILIB_ABI or the new-named equivalent of it, multilib portage is |
22 |
going to fail those checks by using 'default'. |
23 |
|
24 |
Any suggestions how to avoid that? Probably achievable only through |
25 |
staying with $ABI. |
26 |
|
27 |
-- |
28 |
Best regards, |
29 |
Michał Górny |