1 |
Hi all, |
2 |
|
3 |
This only affects linux users. Because in the latest snapshot I was |
4 |
messing with profiles and keywords anyway, I decided to switch linux |
5 |
users to fully qualified GLEP-53-style keywords. This means "x86" |
6 |
becomes "x86-linux" in prefix. Rationale behind this is that the x86 |
7 |
keyword in prefix is not really the same as the x86 keyword in prefix. |
8 |
To stress this distinction, we now use x86-linux. |
9 |
|
10 |
In order to make this fairly painless for linux users, I've modified the |
11 |
profiles such that the ~arch-linux keyword is in ACCEPT_KEYWORDS by |
12 |
default. Since the bootstrap script used (and for linux still does) to |
13 |
a add both the stable and unstable keywords for ~arch, this means all |
14 |
will work well, in the transition period, and even after it. |
15 |
|
16 |
I intend to change the entire tree into X-linux keywords, but not per |
17 |
big bang. I changed my tree update scripts to run "ecleankw" and |
18 |
"ekeyword *.ebuild" prior to committing. "ecleankw" will make sure that |
19 |
"x86" gets transformed into "x86-linux", "ekeyword *.build" will reorder |
20 |
the keywords per OS, secondary per arch. This approach was chosen such |
21 |
that different arch per OS get grouped, which increases the overview |
22 |
(at least for me). |
23 |
|
24 |
If you work with ebuilds and commit them, please make sure you have the |
25 |
latest gentoolkit-dev (for an updated ekeyword) and that you have you |
26 |
tree's scripts dir synced. |
27 |
|
28 |
@devs: |
29 |
As side issue: because I use "ecleankw" when syncing the tree now, it is |
30 |
*even more important* that all keywords that are supported in the tree |
31 |
are listed in the ecleankw script, otherwise they may vanish upon the |
32 |
next sync. |
33 |
|
34 |
|
35 |
-- |
36 |
Fabian Groffen |
37 |
Gentoo on a different level |
38 |
-- |
39 |
gentoo-alt@l.g.o mailing list |