public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Dolbec" <brian.dolbec@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:2.X commit in: targets/support/
Date: Thu, 11 Sep 2014 02:23:50 +0000 (UTC)	[thread overview]
Message-ID: <1409636419.e22f20373f891a718921d5ca47d2c7b8ea0ac31f.dol-sen@gentoo> (raw)

commit:     e22f20373f891a718921d5ca47d2c7b8ea0ac31f
Author:     Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Mon Sep  1 18:12:40 2014 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Tue Sep  2 05:40:19 2014 +0000
URL:        http://sources.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=e22f2037

chroot-functions.sh: Remove --nodeps option from portage update.

This option prevented new deps from being installed with a portage upgrade.

---
 targets/support/chroot-functions.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/targets/support/chroot-functions.sh b/targets/support/chroot-functions.sh
index 5c30537..ce56157 100755
--- a/targets/support/chroot-functions.sh
+++ b/targets/support/chroot-functions.sh
@@ -171,7 +171,7 @@ setup_pkgmgr(){
 	# just let emerge @system could merge it.
 	# Use --update or portage won't reinstall the same version.
 	[ -e /etc/portage/make.conf ] && echo 'USE="${USE} build"' >> /etc/portage/make.conf
-	run_merge --oneshot --nodeps --update sys-apps/portage
+	run_merge --oneshot --update sys-apps/portage
 	sed -i '/USE="${USE} build"/d' /etc/portage/make.conf
 }
 


             reply	other threads:[~2014-09-11  2:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  2:23 Brian Dolbec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-04  2:42 [gentoo-commits] proj/catalyst:2.X commit in: targets/support/ Anthony G. Basile
2018-03-04  2:01 Anthony G. Basile
2017-10-12 19:41 Robin H. Johnson
2016-04-08 21:51 Anthony G. Basile
2016-03-04  1:51 Anthony G. Basile
2014-12-24 14:42 Raúl Porcel
2014-12-07 23:52 Brian Dolbec
2014-11-28 11:41 Raúl Porcel
2014-10-26 12:25 Raúl Porcel
2014-09-11 19:14 Brian Dolbec
2014-09-11  2:23 Brian Dolbec
2014-05-16 19:15 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 Brian Dolbec
2014-03-24 16:08 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=1409636419.e22f20373f891a718921d5ca47d2c7b8ea0ac31f.dol-sen@gentoo \
    --to=brian.dolbec@gmail.com \
    --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