1 |
On Mon, 21 Jan 2013 00:01:05 +0100 |
2 |
Thomas Sachau <tommy@g.o> wrote: |
3 |
|
4 |
> Michał Górny schrieb: |
5 |
> > Hello, |
6 |
> > |
7 |
> > There is a fair interest in multilib and while still early, it would be |
8 |
> > a good moment to decide on how USE flags to use for it. |
9 |
> > |
10 |
> > The current attempts are mostly using USE=multilib which is not really |
11 |
> > expressive and poor. What I would go for is a clear variable specifying |
12 |
> > which targets package is built for. |
13 |
> > |
14 |
> > |
15 |
> > This raises the following questions: |
16 |
> > |
17 |
> > 1) do we want the default ABI to be switchable? |
18 |
> > |
19 |
> > 2) do we want irrelevant ABIs to be visible to emerge users? |
20 |
> > |
21 |
> > By 2) I mean: do we want the users to see stuff like: |
22 |
> > |
23 |
> > MULTILIB_ABIS="amd64_abi1 amd64_abi2 -amd64_abi3 (-ppc64_abi1) |
24 |
> > (-ppc64_abi2) (-ppc64_abi3) ..." |
25 |
> > |
26 |
> > or just the relevant part. |
27 |
> > |
28 |
> > To be honest, I don't know if there's other way to hide USE flags than |
29 |
> > using USE_EXPAND_HIDDEN. If we want to use that, we'd have to split |
30 |
> > the flags per-arch, i.e. have: |
31 |
> > |
32 |
> > MULTILIB_AMD64="abi1 abi2 abi3" |
33 |
> > MULTILIB_PPC64="abi1 abi2 abi3" |
34 |
> > |
35 |
> > with appropriate USE_EXPAND_HIDDEN set by profiles. |
36 |
> > |
37 |
> > |
38 |
> > What are your thoughts? Which arches would like to use multilib? What |
39 |
> > names for ABIs do you suggest? |
40 |
> > |
41 |
> |
42 |
> So you want to re-implement multilib-portage in an eclass without the |
43 |
> additional benefits a package-manager level implementation has? |
44 |
|
45 |
Could you stay on topic, please? |
46 |
|
47 |
-- |
48 |
Best regards, |
49 |
Michał Górny |