1 |
On Mon, 2005-10-31 at 14:22 -0800, Anthony Gorecki wrote: |
2 |
> On Monday, October 31, 2005 13:09, Chris Gianelloni wrote: |
3 |
> > 2. Inform users that only stage3 will be supported |
4 |
> > 3. Change the documentation to recommend users not change USE flags |
5 |
> > until after the completion of "emerge -e system" |
6 |
> |
7 |
> These two options seem to be the most reasonable. If a user doesn't know how |
8 |
> to deploy a system using stage one or two, they should either be instructed |
9 |
> to use stage three, or be given alternate (more cautious) instructions for |
10 |
> the earlier stages. If, on the other hand, the person is familiar with the |
11 |
> inner workings of Gentoo and its packages, they would be likely to ignore the |
12 |
> instructions anyway. |
13 |
|
14 |
We also get bug reports from users using genkernel to build their own |
15 |
CDs using --unionfs-dev, which we don't even list anywhere in the |
16 |
documentation because we know it is broken and it says as much when you |
17 |
use it. |
18 |
|
19 |
The plain and simple truth is that if we allow it *at all* then we will |
20 |
be held responsible for what happens when a user tries to use it, |
21 |
whether they have fore-knowledge of the brokenness or not. |
22 |
|
23 |
> > In pretty much every case, the real answer is "quit using stage1 if you |
24 |
> > don't know what you're doing" but unfortunately, we're going to get the |
25 |
> > pointless "but Gentoo is about choice" "argument" that really has no |
26 |
> > bearing on the truth of what is Gentoo. |
27 |
> |
28 |
> I agree. A section of documentation could be created to explain that concept, |
29 |
> and bugs that were filed as a result of inexperience could then be closed and |
30 |
> redirected to the documentation. |
31 |
|
32 |
I am currently working to have a <warn> section added to the Handbook |
33 |
stating that we highly recommend that users not touch stages 1 or 2. |
34 |
|
35 |
> I use USE="-*" in make.conf for all of my deployments because I don't want the |
36 |
> system's USE flags to be modified by Gentoo developers; I also don't have any |
37 |
> difficulty deploying such systems. Unfortunately, I see many individuals that |
38 |
> will leap to configure their systems in ways that cannot be maintained. In |
39 |
> those cases, the Gentoo developers should not be the ones to correct the |
40 |
> errors. |
41 |
|
42 |
I agree. |
43 |
|
44 |
On the other side of the coin, it is exactly *because* of -* that we |
45 |
have such hacks like nocxx in USE. USE flags are designed for enabling |
46 |
optional support. We should not have no* USE flags. While I personally |
47 |
don't really care either way, it is something that we are currently |
48 |
*required* to do because we have no way to ensure that it will be |
49 |
enabled by default, thanks to -*. Funny enough, I use -* for the same |
50 |
reason as you, but then came to find out about auto-use, and am now glad |
51 |
that I've always used -* myself. ;] |
52 |
|
53 |
-- |
54 |
Chris Gianelloni |
55 |
Release Engineering - Strategic Lead |
56 |
x86 Architecture Team |
57 |
Games - Developer |
58 |
Gentoo Linux |