public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:catalyst_2 commit in: /, targets/support/
Date: Thu, 14 Jul 2011 01:30:14 +0000 (UTC)	[thread overview]
Message-ID: <202e345f8b1910aa17fef4512828ffd5a94e7e15.WilliamH@gentoo> (raw)

commit:     202e345f8b1910aa17fef4512828ffd5a94e7e15
Author:     William Hubbs <w.d.hubbs <AT> gmail <DOT> com>
AuthorDate: Thu Jul 14 01:29:24 2011 +0000
Commit:     William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Thu Jul 14 01:29:24 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=202e345f

Revert "chroot-functions.sh: emerge sys-apps/shadow before distcc"

This reverts commit a4968878f0bf3bf32e0c5fb0c4b6d88a0ebb8084.

Shadow is now built in stage 1, so we do not need this.

---
 ChangeLog                           |    4 ----
 targets/support/chroot-functions.sh |    5 ++---
 2 files changed, 2 insertions(+), 7 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 0e1b89f..b6df4d5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -5,10 +5,6 @@
 
   26 Jun 2011; Matt Turner <mattst88@gentoo.org>
   targets/support/chroot-functions.sh:
-  Emerge sys-apps/shadow before distcc
-
-  26 Jun 2011; Matt Turner <mattst88@gentoo.org>
-  targets/support/chroot-functions.sh:
   Don't run 'distcc-config --install'
 
   26 Jun 2011; Sebastian Pipping <sping@gentoo.org>

diff --git a/targets/support/chroot-functions.sh b/targets/support/chroot-functions.sh
index 0b81e65..e739f0a 100644
--- a/targets/support/chroot-functions.sh
+++ b/targets/support/chroot-functions.sh
@@ -72,19 +72,18 @@ setup_myfeatures(){
 		export clst_myfeatures="${clst_myfeatures} distcc"
 		export DISTCC_HOSTS="${clst_distcc_hosts}"
 		[ -e /etc/make.conf ] && \
-			echo 'USE="${USE} -avahi -gtk -gnome -cracklib -pam"' >> /etc/make.conf
+			echo 'USE="${USE} -avahi -gtk -gnome"' >> /etc/make.conf
 		# We install distcc to / on stage1, then use --noreplace, so we need to
 		# have some way to check if we need to reinstall distcc without being
 		# able to rely on USE, so we check for the distcc user and force a
 		# reinstall if it isn't found.
 		if [ "$(getent passwd distcc | cut -d: -f1)" != "distcc" ]
 		then
-			clst_root_path=/ run_merge --oneshot --nodeps sys-apps/shadow || exit 1
 			clst_root_path=/ run_merge --oneshot --nodeps sys-devel/distcc || exit 1
 		else
 			clst_root_path=/ run_merge --oneshot --nodeps --noreplace sys-devel/distcc || exit 1
 		fi
-		sed -i '/USE="${USE} -avahi -gtk -gnome -cracklib -pam"/d' /etc/make.conf
+		sed -i '/USE="${USE} -avahi -gtk -gnome"/d' /etc/make.conf
 		mkdir -p /etc/distcc
 		echo "${clst_distcc_hosts}" > /etc/distcc/hosts
 



             reply	other threads:[~2011-07-14  1:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14  1:30 William Hubbs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-26 17:06 [gentoo-commits] proj/catalyst:catalyst_2 commit in: /, targets/support/ Matt Turner
2011-06-26 17:06 Matt Turner
2011-06-25 17:52 Matt Turner
2011-04-14 10:20 Raúl Porcel
2011-04-10 17:09 Raúl Porcel

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=202e345f8b1910aa17fef4512828ffd5a94e7e15.WilliamH@gentoo \
    --to=williamh@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