1 |
On Wed, 2005-11-09 at 17:32 +0100, Gregorio Guidi wrote: |
2 |
> > Doing a bootstrap from a stage3 tarball is worthless. You've made it |
3 |
> > sound like users should bootstrap from a stage3 tarball. |
4 |
> > |
5 |
> > While I completely agree that it is all in how you present it, there are |
6 |
> > certain things that we absolutely wish to get away from, and one of them |
7 |
> > is having the user *ever* run bootstrap.sh themselves. |
8 |
> |
9 |
> Sure, I was thinking at the handbook in the followng terms: for users that |
10 |
> want maximum customization (ex stage1 users) it should suggest to untar the |
11 |
> stage, tweak make.conf and run emerge -e system, while for other users (ex |
12 |
> stage3 users) it should suggest to untar the stage and go on with the normal |
13 |
> instructions. |
14 |
|
15 |
I believe that is the general idea, except telling the user to do the |
16 |
"emerge -e system" even on a stage3 tarball should be at the end of the |
17 |
Handbook's install section, simply because it isn't a requirement for |
18 |
installation. |
19 |
|
20 |
Basically, at the end it would say something along the lines of: |
21 |
|
22 |
If you have not already, you can customize your system with your own |
23 |
CFLAGS now. The procedure for updating your complete system is... with |
24 |
some pointers to the various parts of "Using Portage". |
25 |
|
26 |
...or something similar. Honestly, I would leave that up to the better |
27 |
judgement of the GDP. The main goal is to reduce errors generated by |
28 |
our users due to the extreme flexibility of the current setup, while |
29 |
still not removing the choice. I tend to find that if a user has to go |
30 |
elsewhere to read something, they're less likely to do it. This will |
31 |
keep the inexperienced users from doing a stage1-style installation. |
32 |
Truthfully, a person should be familiar with how portage works before |
33 |
doing a stage1-style installation, simply so they can troubleshoot their |
34 |
own issues. |
35 |
|
36 |
-- |
37 |
Chris Gianelloni |
38 |
Release Engineering - Strategic Lead |
39 |
x86 Architecture Team |
40 |
Games - Developer |
41 |
Gentoo Linux |