Gentoo Archives: gentoo-dev

From: Matt Turner <mattst88@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [PATCH] autotools-multilib: wrapper eclass for multilib builds.
Date: Sun, 23 Sep 2012 17:08:28
Message-Id: CAEdQ38GMm0Gs3Oa6MAqwJALYZtv4L7KfxR6WxELcYrY4f64m0g@mail.gmail.com
In Reply to: Re: [gentoo-dev] [PATCH] autotools-multilib: wrapper eclass for multilib builds. by Thomas Sachau
1 On Sun, Sep 23, 2012 at 2:07 AM, Thomas Sachau <tommy@g.o> wrote:
2 > Matt Turner schrieb:
3 >> On Sat, Sep 22, 2012 at 2:24 PM, Michał Górny <mgorny@g.o> wrote:
4 >>> It is a simple eclass using autotools out-of-source builds to build
5 >>> packages for multiple ABIs when multilib is supported.
6 >>
7 >> Thanks a lot, Michał! This looks good to me.
8 >>
9 >>> Use case: xorg packages, ask Matt.
10 >>
11 >> So the idea is that users want up-to-date 32-bit drivers for games and
12 >> WINE. The emul- packages aren't a very good solution for a number of
13 >> reasons.
14 >>
15 >> I'd like to add multilib USE flags to Mesa and thus its dependencies.
16 >> I realized that almost everything in x11-libs/ could be converted very
17 >> easily, which would allow us to get rid of emul-linux-x86-xlibs in
18 >> addition to emul-linux-x86-opengl.
19 >>
20 >>
21 >
22 > This looks like a shortened duplication of a subset of multilib-portage
23 > features. While this wont hurt multilib-portage (since it does exclude
24 > most actions on ebuilds with USE=multilib), it will mean a rewrite for
25 > many ebuilds, which then again need another rewrite (or more likely
26 > revert), when multilib-portage is accepted in a future EAPI.
27
28 I'd much rather have portage handle this for me as well.
29 Unfortunately, the last mail I see about multilib-portage is from two
30 months ago. If it were in EAPI 5, I'd be happy to wait for it. If it
31 even looked like it were progressing, I might wait. But, as you know,
32 gentoo-dev is where ideas go to die.
33
34 As far as ebuild conversions go, this is really simple.
35
36 > So i would prefer some help/support with multilib-portage to get it
37 > accepted sooner, instead of this additional workaround for a subset of
38 > packages.
39
40 That seems like a reasonable request. Let me re-read the previously
41 mentioned thread and get back to you.