Fix a bug that portage didn't get rebuilt with the build use flag

If clst_PGKCACHE is defined, --newuse was not being added to clst_myemergeopts, so then portage was not being rebuilt if portage was already up to date.

diff --git a/targets/support/chroot-functions.sh b/targets/support/chroot-functions.sh
index 5c30537b8c125620e8d0b0f99f7be596f5313ffe..010f52780e0f2c9f6d0411f4f54cc1a4e545cba7 100755 (executable)
--- a/targets/support/chroot-functions.sh
+++ b/targets/support/chroot-functions.sh
@@ -168,10 +168,11 @@ setup_gcc(){
 setup_pkgmgr(){
        # We need to merge our package manager with USE="build" set in case it is
        # portage to avoid frying our /etc/portage/make.conf file.  Otherwise, we could
-       # just let emerge @system could merge it.
-       # Use --update or portage won't reinstall the same version.
+       # just let emerge system could merge it.
+       # Use --update or portage won't reinstall the same version later.
+       # Use --newuse to make sure it rebuilds with the "build" use flag.
        [ -e /etc/portage/make.conf ] && echo 'USE="${USE} build"' >> /etc/portage/make.conf
-       run_merge --oneshot --nodeps --update sys-apps/portage
+       run_merge --oneshot --nodeps --update --newuse  sys-apps/portage
        sed -i '/USE="${USE} build"/d' /etc/portage/make.conf
 }