1 |
On Monday 14 January 2008, Benno Schulenberg wrote: |
2 |
> Bo Ørsted Andresen wrote: |
3 |
> > Furthermore stage 1 is completely unsupported and for a very good |
4 |
> > reason. |
5 |
> |
6 |
> Which good reason, Bo? You seem to know it, so maybe give a link |
7 |
> somewhere; don't make us guess or search. |
8 |
|
9 |
The vast unending stream of completely useless bug reports and requests |
10 |
for help from users who had |
11 |
|
12 |
a) chosen the wrong stage 1 or 2 for their arch |
13 |
b) set the wrong flags and compile options |
14 |
c) listened to ricer advice and been left with an unusable system |
15 |
d) bitch and moan as to why it takes 96 hours to get a bash prompt |
16 |
e) changed the install commands to "something better" which didn't work |
17 |
then consumed too much support time that could have been better spent |
18 |
elsewhere, especially since the answer usually turned out to be "don't |
19 |
try and be clever, just trash what you already did and do it properly |
20 |
with a stage 3" |
21 |
|
22 |
when all of this was completely avoidable if they had just chosen to |
23 |
build from a stage 3 in the first place! |
24 |
|
25 |
A stage 1 has only one purpose in life - to build a stage 2 and to do it |
26 |
in a safe way insulated from any host system. |
27 |
|
28 |
A stage 2 has only one purpose in life - to provide something that can |
29 |
correctly run 'emerge -et system' which produces what you get with a |
30 |
stage 3 install (to a degree of course). |
31 |
|
32 |
So stages 1 and 2 really belong inside catalyst, the more invisible the |
33 |
better (as they are just bootstrap mechanisms). |
34 |
|
35 |
They are still around as catalyst still builds them, if you know where |
36 |
to look they are freely downloadable and can be used. But now when the |
37 |
user makes a hash of it the community can legitimately tell the user to |
38 |
stop wasting their time with unsupported stuff. |
39 |
|
40 |
-- |
41 |
Alan McKinnon |
42 |
alan dot mckinnon at gmail dot com |
43 |
-- |
44 |
gentoo-user@l.g.o mailing list |