1 |
On Mon, 2005-10-31 at 15:53 -0600, Jory A. Pratt wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA1 |
4 |
> |
5 |
> Chris Gianelloni wrote: |
6 |
> > I'm starting to get more and more bugs from users whom have decided, |
7 |
> > against the recommendation of those of us in Release Engineering, to do |
8 |
> > a stage1 or stage2 installation using their custom USE flags, and |
9 |
> > finding that their installation is unable to complete properly. The |
10 |
> > problem stems from more and more packages adding more and more USE |
11 |
> > flags. We already recommend that all users perform a stage3 |
12 |
> > installation, but this doesn't appear to be enough to resolve the |
13 |
> > problem. What it really boils down to is the inability for us to test |
14 |
> > with all of the possible USE flag combinations and ever get a release |
15 |
> > out the door. |
16 |
> > |
17 |
> > As it stands, I only see a few options, none of which sound very good: |
18 |
> > |
19 |
> > 1. Only release stage3 tarballs |
20 |
> > 2. Inform users that only stage3 will be supported |
21 |
> > 3. Change the documentation to recommend users not change USE flags |
22 |
> > until after the completion of "emerge -e system" |
23 |
> > |
24 |
> > In pretty much every case, the real answer is "quit using stage1 if you |
25 |
> > don't know what you're doing" but unfortunately, we're going to get the |
26 |
> > pointless "but Gentoo is about choice" "argument" that really has no |
27 |
> > bearing on the truth of what is Gentoo. Gentoo is *not* about choice. |
28 |
> > Gentoo is about empowering the user to make the system as he sees fit. |
29 |
> > This means there is a certain expectation that when you start fiddling |
30 |
> > with stuff, you're going to pick up the pieces on your own. At any |
31 |
> > rate, the problem is only going to get worse as more and more USE flags |
32 |
> > are added. |
33 |
> > |
34 |
> > What can we do to curb this problem? |
35 |
> > |
36 |
> I am in favor of doing nothing but putting a warning on stage1 and stage |
37 |
> 2 saying only useflags that will be supported are ntpl ntplonly |
38 |
> everything can and should be default IMHO. Then if they run into |
39 |
> problems it is their problem and not ours. As much as we are about |
40 |
> quality we still have a choice and if I choice a stage1 I do it for my |
41 |
> own personal reasons. I am basically favoring do not edit useflags until |
42 |
> stage3 if you make changes at this point you can use emerge -euD system |
43 |
> - --newuse to rebuild packages to support your USE flags. |
44 |
|
45 |
Have you read the bootstrap script? Only nptl, nptlonly, nls, and |
46 |
unicode are currently supported. Everything else is filtered. |
47 |
|
48 |
The problem is the "system" target having more and more packages that |
49 |
have optional components with dependencies on things like a configured |
50 |
kernel, which isn't done until well after the stage3 process is |
51 |
completed. |
52 |
|
53 |
-- |
54 |
Chris Gianelloni |
55 |
Release Engineering - Strategic Lead |
56 |
x86 Architecture Team |
57 |
Games - Developer |
58 |
Gentoo Linux |