fix order of stage1 portage updates
authorRick Farina (Zero_Chaos) <zerochaos@gentoo.org>
Tue, 23 Oct 2012 17:19:51 +0000 (13:19 -0400)
committerRick Farina (Zero_Chaos) <zerochaos@gentoo.org>
Tue, 23 Oct 2012 17:19:51 +0000 (13:19 -0400)
Reorder things based on proper understanding of stage1 builds.
This allows a slight reduction in redundancy.

targets/stage1/stage1-chroot.sh

index 6f7e5b015a22d8e8806987744440975381d9f174..a9536a63fe1fbd53e19c9232fcdef38affe3523e 100644 (file)
@@ -18,15 +18,19 @@ then
        exit 1
 fi
 
+## Setup seed pkgmgr to ensure latest
+clst_root_path=/ setup_pkgmgr
+
 # Update stage3
 if [ -n "${clst_update_seed_cache}" ]; then
        echo "Updating seed stage..."
-       clst_root_path=/ setup_pkgmgr
        clst_root_path=/ run_merge "--update --deep --newuse @world"
 else
        echo "Skipping seed stage update..."
 fi
 
+make_destpath /tmp/stage1root
+
 ## START BUILD
 # First, we drop in a known-good baselayout
 [ -e /etc/portage/make.conf ] && \
@@ -35,10 +39,6 @@ run_merge "--oneshot --nodeps sys-apps/baselayout"
 
 sed -i '/USE="${USE} -build"/d' /etc/portage/make.conf
 
-# Next, we install the package manager
-clst_root_path=/ setup_pkgmgr
-make_destpath /tmp/stage1root
-
 # Now, we install our packages
 [ -e /etc/portage/make.conf ] && \
        echo "USE=\"-* bindist build ${BOOTSTRAP_USE} ${clst_HOSTUSE}\"" \