1 |
Ian Stakenvicius schrieb: |
2 |
> On 25/08/13 10:15 AM, Ulrich Mueller wrote: |
3 |
>>>>>>> On Sun, 25 Aug 2013, Thomas Sachau wrote: |
4 |
> |
5 |
>>> workaround: add a variable, which changes the return of the |
6 |
>>> function checking for the current ABI (always true with variable, |
7 |
>>> without only true, when $ABI == $DEFAULT_ABI) |
8 |
> |
9 |
>> Would this variable be set by the user, in profiles, or in |
10 |
>> ebuilds? |
11 |
> |
12 |
>>> first version (multilib1.patch) directly changes the output of |
13 |
>>> the currently used multilib_is_native_abi() function: |
14 |
> |
15 |
>> I think this would be very misleading. If a function is called |
16 |
>> multilib_is_native_abi then it should test for exactly that, not |
17 |
>> for something else. |
18 |
> |
19 |
> |
20 |
> - From the discussion on this that we had ~2 weeks ago, it seems that |
21 |
> 'multilib_is_native_abi' is only used in the wild now (and only meant |
22 |
> to be used) to handle the cases where we want to say, build everything |
23 |
> for default_abi and only build certain bits for the others. |
24 |
> |
25 |
> If there was a common usage that is important for the actual native |
26 |
> abi (for instance, some sort of check enabling alternate code in a |
27 |
> build system for a specific CHOST or whatnot), then keeping |
28 |
> multilib_is_native_abi as it is would make a lot of sense, but since |
29 |
> there isn't any cases of this I'm not sure it matters -- changing it's |
30 |
> functionality to essentially become multilib_is_default_abi() (whether |
31 |
> we rename it or not) seems to make the most sense to me. |
32 |
|
33 |
While there may currently only be one usecase for the function, it may |
34 |
be used in other cases too with time and wider usage of the new multilib |
35 |
eclasses. If i modify the function for the binaries part, this would |
36 |
require a new function for other usecases. If this really does not |
37 |
happen, the multilib_is_native_abi function could still be deprecated |
38 |
and removed in the future. |
39 |
|
40 |
So i decided to go with a new function. |
41 |
|
42 |
-- |
43 |
|
44 |
Thomas Sachau |
45 |
Gentoo Linux Developer |