From 28c3c3def37f83a7e0a467deebf957be2467bec5 Mon Sep 17 00:00:00 2001 From: Michael Marineau Date: Wed, 8 Jul 2015 13:45:18 -0700 Subject: [PATCH] build_packages: be less aggressive about rebuilding packages The --rebuild-if-unbuilt emerge option will recompile packages if any build-time dependencies changed. This can be a useful safety to make sure applications get re-linked and so forth. However recent versions of portage have grown better defaults for choosing when to rebuild so lets turn the build_packages flag around and leave emerge to do its default behavior and see if that is sufficiently safe. --- build_packages | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/build_packages b/build_packages index b8d6e3cb6f..b4691509ac 100755 --- a/build_packages +++ b/build_packages @@ -49,7 +49,7 @@ DEFINE_string accept_licenses "" \ "Licenses to append to the accept list." DEFINE_integer jobs "${NUM_JOBS}" \ "How many packages to build in parallel at maximum." -DEFINE_boolean norebuild "${FLAGS_FALSE}" \ +DEFINE_boolean rebuild "${FLAGS_FALSE}" \ "Don't automatically rebuild dependencies." DEFINE_boolean skip_chroot_upgrade "${FLAGS_FALSE}" \ "Don't run the chroot upgrade automatically; use with care." @@ -150,7 +150,7 @@ if [[ "${FLAGS_jobs}" -ne -1 ]]; then EMERGE_FLAGS+=( --jobs=${FLAGS_jobs} ) fi -if [[ "${FLAGS_norebuild}" -eq "${FLAGS_FALSE}" ]]; then +if [[ "${FLAGS_rebuild}" -eq "${FLAGS_TRUE}" ]]; then EMERGE_FLAGS+=( --rebuild-if-unbuilt ) fi