1 |
On Wed, Mar 25, 2009 at 8:33 AM, Markus Duft <mduft@g.o> wrote: |
2 |
> this whole proposal would fix multiple problems: |
3 |
> |
4 |
> 1) main and prefix keywords are different, but thats ok if prefix |
5 |
> keywords are PREFIX_KEYWORDS - we could do our own thing here. |
6 |
> |
7 |
> 2) it would solve the problem "how does portage know which packages can |
8 |
> i merge in a prefixed environment" - no need to trigger based on |
9 |
> inherit, EAPI - or something worse :) |
10 |
> |
11 |
> 3) it would ease porting to prefix: simply allow merging main ebeuilds |
12 |
> in prefix by adding GENTOO to the ACCEPT_DISTRO_KEYWORDS. |
13 |
> |
14 |
> 4) it would make gentoo a "real" meta distro as haubi said, since |
15 |
> gentoo's (linux or prefix) "consumers" can do their own thing with |
16 |
> keywords completely different from ours. it would be no problem to use - |
17 |
> for example - keywords like "mduft" and "haubi" (lol), as long as they |
18 |
> are (fex) SALOMON_KEYWORDS. |
19 |
> |
20 |
> what about forwarding this thread to portage-dev@? |
21 |
|
22 |
I'm having trouble formulating a response to haubi's point because it |
23 |
is highly divergent to my main goal(s) here. |
24 |
|
25 |
a) I want non prefix devs[1] to write ebuilds that work in prefix. |
26 |
But, without knowledge of how Gentoo Prefix works - they shouldn't |
27 |
need to know. |
28 |
b) The current strategy of Gentoo Prefix keywords is if it compiles on |
29 |
one arch, it generally will compile on the rest. (Not always true, but |
30 |
mostly true) |
31 |
|
32 |
So, in response to the above points. If we had PREFIX_KEYWORDS, it |
33 |
should _default_ to all and then react to a failure. As in: |
34 |
PREFIX_KEYWORDS="* -x86-interix" |
35 |
|
36 |
-Jeremy |
37 |
|
38 |
[1]: There is no way that the current Prefix dev team can handle all |
39 |
the ebuilds in the main tree. We need to leverage work that other |
40 |
people are already doing - similar to the way linux prefix profiles |
41 |
are inheriting gentoo-x86 profiles. We use the {x86,amd64,ia64} arch |
42 |
teams work to save us from duplicating it. |