1 |
On 02/24/2013 11:39 PM, Samuli Suominen wrote: |
2 |
> On 24/02/13 02:34, hasufell wrote: |
3 |
>> Some people seem to feel uncomfortable with autotools-multilib, because |
4 |
>> it depends on autotools-utils. |
5 |
>> |
6 |
>> Instead of arguing whether it makes sense or not I'd propose a similar |
7 |
>> autotools related eclass. |
8 |
>> |
9 |
>> I also attach an example conversion of media-libs/libexif (the |
10 |
>> maintainer wants to keep the changes minimal). |
11 |
>> Effectively I am only (almost) changing the function names and not the |
12 |
>> ebuild code. |
13 |
> |
14 |
> looks good, seems exactly what I wanted |
15 |
> |
16 |
>> Feel free to propose a different eclass name. |
17 |
> |
18 |
> whatever it will be, please make it shorter, like 'multiabi' maybe |
19 |
> |
20 |
|
21 |
I cleaned up some things. |
22 |
|
23 |
1) eclass renamed to multilib-minimal.eclass |
24 |
prepabisources() renamed to multilib_copy_sources() |
25 |
|
26 |
2) if someone wants out-of-source builds he gotta handle that manually, |
27 |
as in: not calling multilib_copy_sources and making sure that stuff like |
28 |
ECONF_SOURCE is set correctly |
29 |
(${BUILD_DIR} will be created unconditionally in src_configure anyway) |
30 |
|
31 |
3) all autotools related code removed |
32 |
|
33 |
4) Introduced a DISABLE_MULTILIB variable for use of portage-multilib, |
34 |
which will disable all multilib related stuff. I am not sure if that's |
35 |
what they want, but I heard something like that. |
36 |
Tommy should comment on this. |
37 |
|
38 |
In case this eclass will be deprecated at some point, conversion back to |
39 |
normal will be trivial anyway. |