| 1 |
On Sun, 2005-11-06 at 22:41 +0000, Peter Humphrey wrote: |
| 2 |
> On Sun, 6 Nov 2005 19:27:26 +0100 |
| 3 |
> Sven Vermeulen <swift@g.o> wrote: |
| 4 |
> |
| 5 |
> > I'd like to have the stages/ directory only contain stage3 files and |
| 6 |
> > have the stage1/2's in experimental or similar. |
| 7 |
> |
| 8 |
> If most of us are to be advised to use only stage 3 for installation, |
| 9 |
> that will remove one of the main advantages of Gentoo, namely having |
| 10 |
> everything compiled on the machine it's running on. What advice will be |
| 11 |
> offered on remerging first the toolkit, then the system packages and |
| 12 |
> then the world files? Is maguire's emwrap script to be promoted? |
| 13 |
> (http://forums.gentoo.org/viewtopic-t-282474-postdays-0-postorder-asc-start-200.html) |
| 14 |
|
| 15 |
It removes 0 advantages. |
| 16 |
|
| 17 |
Why are you spreading such blatant misinformation? |
| 18 |
|
| 19 |
Exactly what is gained by compiling the toolchain twice on your system? |
| 20 |
What do you gain that can not be accomplished by using a stage3 tarball, |
| 21 |
editing make.conf, and running an emerge -e system? |
| 22 |
|
| 23 |
The main point is pretty simple. There is 0 reason to compile the |
| 24 |
toolchain twice. You gain 0 performance. You gain 0 customization |
| 25 |
options. You lose quite a bit of time and introduce countless |
| 26 |
possibilities for errors that are completely user-created that get |
| 27 |
pushed onto the Release Engineering team to "support". |
| 28 |
|
| 29 |
Think about this. |
| 30 |
|
| 31 |
nano -w /etc/make.conf |
| 32 |
scripts/bootstrap.sh |
| 33 |
emerge -e system |
| 34 |
|
| 35 |
Now, think about this. |
| 36 |
|
| 37 |
tar xjpf /mnt/cdrom/stage3-x86-2005.1.tar.bz2 |
| 38 |
nano -w /etc/make.conf |
| 39 |
emerge -e system |
| 40 |
|
| 41 |
Both produce the same output when you are done. Both give you a |
| 42 |
customized system with *your* choices of USE and CFLAGS. However, only |
| 43 |
the stage3 method *ensures* that you have a complete and usable system |
| 44 |
to perform your installation. The only thing that you have done by |
| 45 |
adding in the bootstrap step is you have compiled the toolchain twice, |
| 46 |
with 0 net gain. |
| 47 |
|
| 48 |
-- |
| 49 |
Chris Gianelloni |
| 50 |
Release Engineering - Strategic Lead |
| 51 |
x86 Architecture Team |
| 52 |
Games - Developer |
| 53 |
Gentoo Linux |
Archives