1 |
On Wed, 2009-03-25 at 11:44 +0100, Michael Haubenwallner wrote: |
2 |
> On Wed, 2009-03-25 at 07:50 +0100, Markus Duft wrote: |
3 |
> > On Wed, 2009-03-25 at 00:30 -0500, Jeremy Olexa wrote: |
4 |
> |
5 |
> > > Any other thoughts? |
6 |
> |
7 |
> > however i talked to haubi a while back about keywords. he for sure has |
8 |
> > some more wise words to say :) |
9 |
> |
10 |
> LOL! |
11 |
> But indeed, my brain cooks an idea for some time now - time to serve |
12 |
> (thank you for the trigger!): |
13 |
|
14 |
:) |
15 |
|
16 |
> |
17 |
[snip] |
18 |
> Now I want to tell PM which ebuild-keywords to use for my |
19 |
> distro-instance, where only 1. and 2. really would make sense (sample |
20 |
> for non-Prefix): |
21 |
> 1. 'amd64 hppa ~x86' |
22 |
> 2. 'amd64 hppa ~mips ~ppc ~x86' |
23 |
> 3. 'amd64 hppa ~mips ~ppc x86' |
24 |
> 4. '~amd64 ~hppa ~mips ~ppc ~x86' |
25 |
> 5. 'amd64 ~hppa ~mips ~ppc x86' |
26 |
> |
27 |
> This could be done by telling PM how to merge KEYWORDS and |
28 |
> HAUBIDIST_KEYWORDS in etc/make.conf or profile/make.conf, like: |
29 |
> 1. ACCEPT_DISTRO_KEYWORDS='HAUBIDIST' |
30 |
> 2. ACCEPT_DISTRO_KEYWORDS='HAUBIDIST ~GENTOO' |
31 |
> 3. ACCEPT_DISTRO_KEYWORDS='HAUBIDIST GENTOO' |
32 |
> 4. ACCEPT_DISTRO_KEYWORDS='~HAUBIDIST GENTOO' |
33 |
> 5. ACCEPT_DISTRO_KEYWORDS='GENTOO ~HAUBIDIST' |
34 |
> where 'HAUBIDIST' maps to 'HAUBIDIST_KEYWORDS' and 'GENTOO' maps to |
35 |
> 'KEYWORDS'. |
36 |
> |
37 |
> This eventually also could apply for Gentoo Hardened, to not have that |
38 |
> large list in package.mask, but HARDENED_KEYWORDS in the ebuilds, and |
39 |
> ACCEPT_DISTRO_KEYWORDS='HARDENED ~GENTOO' in make.conf. |
40 |
> |
41 |
> Because both KEYWORDS and HARDENED_KEYWORDS would be in upstream ebuild, |
42 |
> this also could work for HAUBIDIST in make.conf: |
43 |
> ACCEPT_DISTRO_KEYWORDS='HAUBIDIST ~HARDENED' |
44 |
> |
45 |
> For Prefix: |
46 |
> |
47 |
> We could have PREFIX_KEYWORDS in the maintree-ebuild, and for HAUBIDIST |
48 |
> - when it is a Prefix distro - to have in make.conf: |
49 |
> ACCEPT_DISTRO_KEYWORDS='HAUBIDIST ~PREFIX' |
50 |
> |
51 |
> For the vanilla "Gentoo Prefix Distribution", this would mean to have: |
52 |
> ACCEPT_DISTRO_KEYWORDS='PREFIX' |
53 |
> the vanilla "Gentoo Linux Distribution" would ship with: |
54 |
> ACCEPT_DISTRO_KEYWORDS='GENTOO' |
55 |
> and the vanilla "Gentoo Hardened Linux Distribution" with: |
56 |
> ACCEPT_DISTRO_KEYWORDS='HARDENED' |
57 |
> |
58 |
> What else would be needed for the whole topic: |
59 |
> * helpers to manage/merge/update my private distro-tree. |
60 |
> * helpers to set up my private distro-mirror. |
61 |
> * repoman support for additional keyword variables |
62 |
> * ... |
63 |
|
64 |
this whole proposal would fix multiple problems: |
65 |
|
66 |
1) main and prefix keywords are different, but thats ok if prefix |
67 |
keywords are PREFIX_KEYWORDS - we could do our own thing here. |
68 |
|
69 |
2) it would solve the problem "how does portage know which packages can |
70 |
i merge in a prefixed environment" - no need to trigger based on |
71 |
inherit, EAPI - or something worse :) |
72 |
|
73 |
3) it would ease porting to prefix: simply allow merging main ebeuilds |
74 |
in prefix by adding GENTOO to the ACCEPT_DISTRO_KEYWORDS. |
75 |
|
76 |
4) it would make gentoo a "real" meta distro as haubi said, since |
77 |
gentoo's (linux or prefix) "consumers" can do their own thing with |
78 |
keywords completely different from ours. it would be no problem to use - |
79 |
for example - keywords like "mduft" and "haubi" (lol), as long as they |
80 |
are (fex) SALOMON_KEYWORDS. |
81 |
|
82 |
what about forwarding this thread to portage-dev@? |
83 |
|
84 |
Cheers, Markus |
85 |
|
86 |
> |
87 |
> </braindump> |
88 |
> |
89 |
> Thoughts? |
90 |
> |
91 |
> /haubi/ |