Make sure portage updates itself at the start of stage1 - thanks to Zac for noticing...

diff --git a/targets/support/chroot-functions.sh b/targets/support/chroot-functions.sh
index c454aaf1c580d9a158026f81f91f7fcecd118096..af693e8ccbbd1a393260e50a72a7105a7a874fd6 100644 (file)
--- a/targets/support/chroot-functions.sh
+++ b/targets/support/chroot-functions.sh
@@ -165,8 +165,9 @@ setup_pkgmgr(){
        # We need to merge our package manager with USE="build" set in case it is
        # portage to avoid frying our /etc/make.conf file.  Otherwise, we could
        # just let emerge system could merge it.
+       # Use --update or portage won't reinstall the same version.
        [ -e /etc/make.conf ] && echo 'USE="${USE} build"' >> /etc/make.conf
-       run_merge --oneshot --nodeps sys-apps/portage
+       run_merge --oneshot --nodeps --update sys-apps/portage
        sed -i '/USE="${USE} build"/d' /etc/make.conf
 }