From e7ea409acb52b43e9ea141c57201f9f87673f7ba Mon Sep 17 00:00:00 2001 From: "Rick Farina (Zero_Chaos)" Date: Wed, 30 Jan 2013 22:57:36 -0500 Subject: [PATCH] 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 --- targets/stage1/stage1-chroot.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/targets/stage1/stage1-chroot.sh b/targets/stage1/stage1-chroot.sh index 462ea283..3f628c22 100644 --- 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}" -- 2.26.2