public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Dolbec" <dolsen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:pending commit in: targets/stage1/
Date: Tue,  1 Sep 2015 05:58:56 +0000 (UTC)	[thread overview]
Message-ID: <1440909094.ceafc1abfdffb34e1dc0f5e1d9ec08c02f189786.dolsen@gentoo> (raw)

commit:     ceafc1abfdffb34e1dc0f5e1d9ec08c02f189786
Author:     Jorge Manuel B. S. Vicetto (jmbsvicetto) <jmbsvicetto <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 30 04:31:34 2015 +0000
Commit:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
CommitDate: Sun Aug 30 04:31:34 2015 +0000
URL:        https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=ceafc1ab

Don't use BOOTSTRAP_USE to update the seed but just build and bindist (if set).

Signed-off-by: Jorge Manuel B. S. Vicetto (jmbsvicetto) <jmbsvicetto <AT> gentoo.org>

 targets/stage1/stage1-chroot.sh | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/targets/stage1/stage1-chroot.sh b/targets/stage1/stage1-chroot.sh
index 01ef8d1..ebd6551 100755
--- a/targets/stage1/stage1-chroot.sh
+++ b/targets/stage1/stage1-chroot.sh
@@ -7,7 +7,8 @@ export clst_buildpkgs="$(/tmp/build.py)"
 
 # Setup our environment
 BOOTSTRAP_USE="$(portageq envvar BOOTSTRAP_USE)"
-[ -n "${clst_BINDIST}" ] && BOOTSTRAP_USE="${BOOTSTRAP_USE} bindist"
+[ -n "${clst_BINDIST}" ] && BINDIST="bindist"
+BOOTSTRAP_USE="${BOOTSTRAP_USE} ${BINDIST}"
 
 FEATURES="${clst_myfeatures} nodoc noman noinfo -news"
 
@@ -26,8 +27,8 @@ clst_root_path=/ setup_pkgmgr "build"
 # Update stage3
 if [ -n "${clst_update_seed}" ]; then
 	if [ "${clst_update_seed}" == "yes" ]; then
-		# We might need BOOTSTRAP_USE to avoid blocks related to bindist use flag
-		[ -e ${clst_make_conf} ] && echo "USE=\"${USE} ${BOOTSTRAP_USE}\"" >> ${clst_make_conf}
+		# Set USE flags build and bindist if clst_BINDIST is set
+		[ -e ${clst_make_conf} ] && echo "USE=\"${USE} build ${BINDIST}" >> ${clst_make_conf}
 
 		echo "Updating seed stage..."
 		if [ -n "${clst_update_seed_command}" ]; then
@@ -37,7 +38,7 @@ if [ -n "${clst_update_seed}" ]; then
 		fi
 
 		# Clean-up USE again
-		sed -i "/USE=\"${USE} ${BOOTSTRAP_USE}\"/d" ${clst_make_conf}
+		sed -i "/USE=\"${USE} build ${BINDIST}\"/d" ${clst_make_conf}
 
 	elif [ "${clst_update_seed}" != "no" ]; then
 		echo "Invalid setting for update_seed: ${clst_update_seed}"


             reply	other threads:[~2015-09-01  5:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01  5:58 Brian Dolbec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-29 17:20 [gentoo-commits] proj/catalyst:master commit in: targets/stage1/ Brian Dolbec
2017-11-22 15:52 ` [gentoo-commits] proj/catalyst:pending " Brian Dolbec
2017-03-16 22:57 Brian Dolbec
2017-03-11  9:35 Brian Dolbec
2017-03-11  7:07 Brian Dolbec
2015-09-08 14:14 Brian Dolbec
2015-09-03 15:14 Brian Dolbec
2015-09-01  5:58 Brian Dolbec
2015-09-01  5:58 Brian Dolbec
2015-09-01  5:58 Brian Dolbec
2015-05-21 23:53 Brian Dolbec
2014-09-02  5:54 Brian Dolbec
2014-09-02  2:43 Brian Dolbec
2014-01-22 15:52 Brian Dolbec
2014-01-22 15:52 Brian Dolbec
2014-01-03  6:41 Brian Dolbec
2014-01-03  6:41 Brian Dolbec
2014-01-03  6:12 Brian Dolbec
2014-01-03  6:12 Brian Dolbec
2014-01-03  5:03 Brian Dolbec
2014-01-03  5:03 Brian Dolbec
2014-01-02  0:04 Brian Dolbec
2014-01-02  0:04 Brian Dolbec
2013-12-31 18:14 Brian Dolbec
2013-12-31 18:14 Brian Dolbec
2013-12-31  4:48 Brian Dolbec
2013-12-31  4:48 Brian Dolbec
2013-12-31  4:39 Brian Dolbec
2013-12-31  4:39 Brian Dolbec
2013-12-31  4:22 Brian Dolbec
2013-12-31  4:22 Brian Dolbec
2013-12-30  1:44 Brian Dolbec
2013-12-30  1:44 Brian Dolbec
2013-12-20  0:48 Brian Dolbec
2013-12-20  0:48 Brian Dolbec
2013-12-20  0:29 Brian Dolbec
2013-12-20  0:29 Brian Dolbec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1440909094.ceafc1abfdffb34e1dc0f5e1d9ec08c02f189786.dolsen@gentoo \
    --to=dolsen@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox