| 1 |
> Think about this. |
| 2 |
> |
| 3 |
> nano -w /etc/make.conf |
| 4 |
> scripts/bootstrap.sh |
| 5 |
> emerge -e system |
| 6 |
> |
| 7 |
> Now, think about this. |
| 8 |
> |
| 9 |
> tar xjpf /mnt/cdrom/stage3-x86-2005.1.tar.bz2 |
| 10 |
> nano -w /etc/make.conf |
| 11 |
> emerge -e system |
| 12 |
> |
| 13 |
> Both produce the same output when you are done. Both give you a |
| 14 |
> customized system with *your* choices of USE and CFLAGS. However, only |
| 15 |
> the stage3 method *ensures* that you have a complete and usable system |
| 16 |
> to perform your installation. The only thing that you have done by |
| 17 |
> adding in the bootstrap step is you have compiled the toolchain twice, |
| 18 |
> with 0 net gain. |
| 19 |
|
| 20 |
When you use the stage 3 method and disable some USE-flags in make.conf that |
| 21 |
were used when building the stage3-file, what is the suggested method? |
| 22 |
|
| 23 |
nano -w /etc/make.conf |
| 24 |
scripts/bootstrap.sh |
| 25 |
emerge -e system |
| 26 |
|
| 27 |
or |
| 28 |
|
| 29 |
nano -w /etc/make.conf |
| 30 |
emerge -e system |
| 31 |
emerge --depclean |
| 32 |
revdep-rebuild |
| 33 |
|
| 34 |
or? |
| 35 |
-- |
| 36 |
gentoo-doc@g.o mailing list |
Archives