| 1 |
On Thu, 28 Feb 2013 02:06:25 +0100 |
| 2 |
hasufell <hasufell@g.o> wrote: |
| 3 |
|
| 4 |
> On 02/24/2013 11:39 PM, Samuli Suominen wrote: |
| 5 |
> > On 24/02/13 02:34, hasufell wrote: |
| 6 |
> >> Some people seem to feel uncomfortable with autotools-multilib, because |
| 7 |
> >> it depends on autotools-utils. |
| 8 |
> >> |
| 9 |
> >> Instead of arguing whether it makes sense or not I'd propose a similar |
| 10 |
> >> autotools related eclass. |
| 11 |
> >> |
| 12 |
> >> I also attach an example conversion of media-libs/libexif (the |
| 13 |
> >> maintainer wants to keep the changes minimal). |
| 14 |
> >> Effectively I am only (almost) changing the function names and not the |
| 15 |
> >> ebuild code. |
| 16 |
> > |
| 17 |
> > looks good, seems exactly what I wanted |
| 18 |
> > |
| 19 |
> >> Feel free to propose a different eclass name. |
| 20 |
> > |
| 21 |
> > whatever it will be, please make it shorter, like 'multiabi' maybe |
| 22 |
> > |
| 23 |
> |
| 24 |
> I cleaned up some things. |
| 25 |
> |
| 26 |
> 1) eclass renamed to multilib-minimal.eclass |
| 27 |
|
| 28 |
You didn't like multilib-wrapper? |
| 29 |
|
| 30 |
> 4) Introduced a DISABLE_MULTILIB variable for use of portage-multilib, |
| 31 |
> which will disable all multilib related stuff. I am not sure if that's |
| 32 |
> what they want, but I heard something like that. |
| 33 |
> Tommy should comment on this. |
| 34 |
|
| 35 |
Setting that variable would invalidate metadata cache. |
| 36 |
|
| 37 |
-- |
| 38 |
Best regards, |
| 39 |
Michał Górny |
Archives