| 1 |
Michał Górny schrieb: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> Following all the suggestions from Alexis Ballier, I have reworked |
| 5 |
> the code to remove multiple points of failure. I have also rebased it |
| 6 |
> on the common multilib-build eclass concept, and updated amd64 |
| 7 |
> no-multilib & x86 profiles as well. |
| 8 |
> |
| 9 |
> Key points: |
| 10 |
> |
| 11 |
> 1. The list of available flags and corresponding ABIs is now stored |
| 12 |
> in a single variable. Adding a new ABI is as simple as adding |
| 13 |
> a value to that variable (+ profiles). |
| 14 |
> |
| 15 |
> 2. All ABIs are validated against $(get_all_abis) list. This guarantees |
| 16 |
> that we check only the flags proper for the arch. |
| 17 |
> |
| 18 |
> 3. The USE_EXPAND is visible only on amd64 multilib profile. However, |
| 19 |
> it is also available on non-multilib amd64 & x86, with all flags |
| 20 |
> masked except for the default one which is force-enabled. |
| 21 |
> |
| 22 |
> The last point means that x86 binary packages (skype) can have |
| 23 |
> dependencies as simple as: |
| 24 |
> |
| 25 |
> dev-libs/libfoo[abi_x86_32] |
| 26 |
> |
| 27 |
> which would be valid both for amd64 multilib & x86. |
| 28 |
> |
| 29 |
> |
| 30 |
> |
| 31 |
|
| 32 |
Lets see, if i understand your plan right, without reading all your diffs: |
| 33 |
|
| 34 |
1. you currently support amd64/multilib and show same flags on |
| 35 |
amd64/no-multilib and x86 to avoid duplicating the dependency list? If |
| 36 |
yes, will this be extended to general support for all multilib arches, |
| 37 |
only on request for specific arches or not at all? |
| 38 |
|
| 39 |
2. How do you handle other abi-specific files like headers or binaries |
| 40 |
and cases like binaries with abi-specific content? Is it possible to |
| 41 |
preserve them for all requested abis or to preserve them for an |
| 42 |
non-default abi? |
| 43 |
|
| 44 |
-- |
| 45 |
|
| 46 |
Thomas Sachau |
| 47 |
Gentoo Linux Developer |
Archives