1 |
On Sun, 23 Sep 2012 12:33:58 +0200 |
2 |
Pacho Ramos <pacho@g.o> wrote: |
3 |
|
4 |
> El dom, 23-09-2012 a las 11:56 +0200, Michał Górny escribió: |
5 |
> > On Sun, 23 Sep 2012 11:07:30 +0200 |
6 |
> > Thomas Sachau <tommy@g.o> wrote: |
7 |
> > |
8 |
> > > Matt Turner schrieb: |
9 |
> > > > On Sat, Sep 22, 2012 at 2:24 PM, Michał Górny <mgorny@g.o> wrote: |
10 |
> > > >> It is a simple eclass using autotools out-of-source builds to build |
11 |
> > > >> packages for multiple ABIs when multilib is supported. |
12 |
> > > > |
13 |
> > > > Thanks a lot, Michał! This looks good to me. |
14 |
> > > > |
15 |
> > > >> Use case: xorg packages, ask Matt. |
16 |
> > > > |
17 |
> > > > So the idea is that users want up-to-date 32-bit drivers for games and |
18 |
> > > > WINE. The emul- packages aren't a very good solution for a number of |
19 |
> > > > reasons. |
20 |
> > > > |
21 |
> > > > I'd like to add multilib USE flags to Mesa and thus its dependencies. |
22 |
> > > > I realized that almost everything in x11-libs/ could be converted very |
23 |
> > > > easily, which would allow us to get rid of emul-linux-x86-xlibs in |
24 |
> > > > addition to emul-linux-x86-opengl. |
25 |
> > > > |
26 |
> > > > |
27 |
> > > |
28 |
> > > This looks like a shortened duplication of a subset of multilib-portage |
29 |
> > > features. While this wont hurt multilib-portage (since it does exclude |
30 |
> > > most actions on ebuilds with USE=multilib), it will mean a rewrite for |
31 |
> > > many ebuilds, which then again need another rewrite (or more likely |
32 |
> > > revert), when multilib-portage is accepted in a future EAPI. |
33 |
> > |
34 |
> > s/when/if/ |
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 |
> > I prefer the simpler solution. |
41 |
> > |
42 |
> > > P.S.: I know, that users, who want up-to-date 32bit drivers for games |
43 |
> > > and wine do use multilib-portage, so we already have a working solution |
44 |
> > > for this issue. |
45 |
> > |
46 |
> > They will no longer have to do that. |
47 |
> > |
48 |
> |
49 |
> I would prefer if eclass way could be extended to packages not using |
50 |
> autotools too, otherwise, we will still need emul packages for, for |
51 |
> example, qt libs. If that would be possible via eclass, maybe |
52 |
> multilib-portage wouldn't be needed but, if not, we will still need it |
53 |
> and, then, would be nice if this inclussion for autotools packages |
54 |
> wouldn't cause more problems to get the "strong" solution land in the |
55 |
> "near" future :/ |
56 |
> |
57 |
> The simpler solution (eclass) looks fine to me, but it would need to be |
58 |
> extended to more packages than autotools based ones to let it replace |
59 |
> portage-multilib/emul packages |
60 |
|
61 |
Qt uses cmake, doesn't it? |
62 |
|
63 |
I don't mind having cmake-multilib as well? We could probably move |
64 |
the foreach_abi() function to some more common eclass, like multilib |
65 |
eclass. |
66 |
|
67 |
-- |
68 |
Best regards, |
69 |
Michał Górny |