don't build packages during update_seed

when update_seed is run it uses the default catalyst emerge options
which causes binary packages to be built which are linked against the
seed stage rather than the generated stage.  These binary packages
can be later used and cause significant and odd issues due to being
linked to older libraries.  I am passing "--buildpkg=n" for the
update_seed runs to prevent this issue and close bug #454184

diff --git a/targets/stage1/stage1-chroot.sh b/targets/stage1/stage1-chroot.sh
index 462ea28387fa3678ab51507d783ca671d18c0f96..3f628c22cfcb97ba45fa01b594c17b0cc465b7f8 100644 (file)
--- a/targets/stage1/stage1-chroot.sh
+++ b/targets/stage1/stage1-chroot.sh
@@ -28,9 +28,9 @@ if [ -n "${clst_update_seed}" ]; then
        if [ "${clst_update_seed}" == "yes" ]; then
                echo "Updating seed stage..."
                if [ -n "${clst_update_seed_command}" ]; then
-                       clst_root_path=/ run_merge "${clst_update_seed_command}"
+                       clst_root_path=/ run_merge "--buildpkg=n ${clst_update_seed_command}"
                else
-                       clst_root_path=/ run_merge "--update --deep --newuse --onlydeps gcc"
+                       clst_root_path=/ run_merge "--buildpkg=n --update --deep --newuse --onlydeps gcc"
                fi
        elif [ "${clst_update_seed}" != "no" ]; then
                echo "Invalid setting for update_seed: ${clst_update_seed}"