| 1 |
On Wed, 2006-01-25 at 23:27 +0100, Sven Köhler wrote: |
| 2 |
> IMHO, i would expect that "/usr/portage/scripts/bootstrap.sh; emerge -e |
| 3 |
> system" results in a system, that has a certain "integrity" with a |
| 4 |
> minimum of manual steps. (gentoo install being as easy as possible) |
| 5 |
|
| 6 |
That has never been the case. The entire *point* of bootstrap is so |
| 7 |
that you can *customize* the system. If you're doing |
| 8 |
"/usr/portage/scripts/bootstrap.sh; emerge -e system" with no |
| 9 |
customization, you're wasting your time. You get identical results from |
| 10 |
a "stage3 tarball + edit make.conf + emerge -e system + emerge -v |
| 11 |
depclean", and it is a faster method, too. |
| 12 |
|
| 13 |
> At the moment, "/usr/portage/scripts/bootstrap.sh; emerge -e system" |
| 14 |
> produces a system, that is IMHO unexpected for most users. |
| 15 |
|
| 16 |
This is exactly why we do not recommend a stage1 installation to anyone |
| 17 |
that is unwilling to do work to modify the installation themselves. |
| 18 |
Using stage1 assumes that you know what you are doing. |
| 19 |
|
| 20 |
> That's not a problem for me. So excuse me that i wanted |
| 21 |
> gentoo-installation to be more simple. |
| 22 |
|
| 23 |
It is quite simple. The documentation is quite extensive on installing |
| 24 |
from a stage3 tarball. How much simpler can you get? ;] |
| 25 |
|
| 26 |
-- |
| 27 |
Chris Gianelloni |
| 28 |
Release Engineering - Strategic Lead |
| 29 |
x86 Architecture Team |
| 30 |
Games - Developer |
| 31 |
Gentoo Linux |
Archives