1 |
Alright, so I'm guessing that we're going with NPTL for 2006.0, except |
2 |
on arches where the arch team has determined that it isn't stable, or |
3 |
that doesn't have a stable 2.6 headers/kernels. |
4 |
|
5 |
Here's what I've done for x86, and I really encourage all of you to |
6 |
follow suit. |
7 |
|
8 |
I've created a no-nptl sub-profile that has "nptl nptlonly" in use.mask, |
9 |
along with a 2.4 sub-profile. This 2.4 sub-profile will be *the* 2.4 |
10 |
sub-profile for x86, with the other 2.4 profiles being deprecated. I |
11 |
have added "nptl" to USE for the 2006.0 profile, and *not* for the "x86" |
12 |
profile. Also, because x86 supports 2.4-based systems, I have *not* |
13 |
added STAGE1_USE="nptl". If your architecture is on 2.6-only, then you |
14 |
are free to add this to your profile. I highly recommend *against* |
15 |
adding nptlonly to STAGE1_USE or USE at this time. I have also |
16 |
minimized the USE flags enabled in the default-linux/x86 profile. This |
17 |
makes the profile very usable for non-release sub-profiles, by limiting |
18 |
the number of USE someone is forced to disable. All of the other USE |
19 |
flags are enabled in the sub-profiles for each release. |
20 |
|
21 |
So... there's my "lead by example" so much as it applies. Feel free to |
22 |
make any arch-specific changes you wish to your own profiles, but I've |
23 |
given you what I plan on doing on x86 for the future. |
24 |
|
25 |
-- |
26 |
Chris Gianelloni |
27 |
Release Engineering - Strategic Lead |
28 |
x86 Architecture Team |
29 |
Games - Developer |
30 |
Gentoo Linux |