the --newuse take in account of "bootstrap" and "build" use flags, and to rebuild few (but heavy) apps. There are 3 alternatives: 1) it's correct, and the apps *need* to be rebuilt In this case, should be documented and become a step of the installation guide http://www.gentoo.org/doc/en/gentoo-*-quickinstall.xml http://www.gentoo.org/doc/en/handbook/2004.3/handbook-*.xml 2) It's useless (in this case is strange the popt emerge, see below) 3) I'm missing something, happen 3a) 1 and 2 applyes to different packages # emerge -uDpv --newuse world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild R ] sys-libs/db-4.2.52_p2 -bootstrap* -doc -java -nocxx -tcltk 0 kB [ebuild R ] dev-lang/python-2.3.4 -X +berkdb -bootstrap* -build -debug -doc +gdbm -ipv6 +ncurses +readline +ssl -tcltk -ucs2 0 kB [ebuild R ] sys-devel/gcc-3.4.3.20050110 -bootstrap* -boundschecking -build -debug -fortran -gcj -gtk -hardened (-ip28) (-multilib) -multislot (-n32) (-n64) +nls -nocxx -objc -static (-uclibc) 0 kB [ebuild R ] sys-apps/sysvinit-2.86 -bootstrap* -build (-selinux) 0 kB [ebuild R ] sys-apps/baselayout-1.11.9-r1 -bootstrap* -build -debug -livecd -static (-uclibc) 0 kB [ebuild R ] sys-apps/sed-4.1.2 -bootstrap* -build -debug +nls -static 0 kB [ebuild R ] app-arch/ncompress-4.2.4-r1 -build* 0 kB [ebuild R ] sys-apps/file-4.12 -build* -debug -python 0 kB [ebuild N ] dev-libs/popt-1.7-r1 +nls 0 kB [ebuild R ] net-misc/rsync-2.6.3 -acl -build* -debug -ipv6 -static 0 kB [ebuild R ] sys-devel/make-3.80-r1 -build* -debug +nls* -static (-uclibc) 0 kB [ebuild R ] sys-apps/findutils-4.1.20-r1 -afs -build* -debug +nls* (-selinux) -static 0 kB Total size of downloads: 0 kB best regards francesco
It wouldn't hurt if this became part of the docs. It'd be beneficial to get this information out. It might be nice if catalyst handled this as well for the higher number stages. emerge -uD --newuse system would do quite nicely instead of 'emerge system' or it's normal variants.
Actually, the docs have already been updated for 2005.0 to give three choices. 1. The user can simply do "emerge system" and only new portions of their system will be rebuilt with their new USE/CFLAGS, anything made during bootstrap will remain as compiled at that time. This is the quickest method. 2. The user can do an "emerge --newuse system" and it will compile the new portions of their system with their new USE/CFLAGS, and anything made during bootstrap that has had changed USE flags will be rebuilt. 3. The user can do an "emerge -e system" and it will recompile everything using their new USE/CFLAGS. This is obviously the slowest method, but this ensures that every package is completely recompiled using the user's given USE/CFLAGS. This really is not required for 2004.3 or earlier, but due to the changes in the stages for 2005.0, these options are all being presented.
is a package built by bootstrap (thus with USE="build") the same as one built without? what exactly does this flag do? (i can't find this in documentation anywhere)
Is there anything else that needs to be done for this bug?
Nope... we've documented this for 2005.0 and beyond
Done then. :)
