From 72f9ddefe49ab1b24196161a07587aac3cdfdd04 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Wed, 16 Nov 2011 10:43:51 -0800 Subject: emerge --quiet-build: don't set PORTAGE_QUIET The PORTAGE_QUIET controls lots of stuff that really should only be controlled by --quiet, especially now that --quiet-build is enabled by default. For example, PORTAGE_QUIET supresses the successful checksum display that is produced by emerge --fetchonly. --- pym/_emerge/actions.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'pym/_emerge/actions.py') diff --git a/pym/_emerge/actions.py b/pym/_emerge/actions.py index 4a72ff471..ba2e631f2 100644 --- a/pym/_emerge/actions.py +++ b/pym/_emerge/actions.py @@ -2707,7 +2707,7 @@ def adjust_config(myopts, settings): if "--buildpkg" in myopts: settings.features.add("buildpkg") - if "--quiet" in myopts or "--quiet-build" in myopts: + if "--quiet" in myopts: settings["PORTAGE_QUIET"]="1" settings.backup_changes("PORTAGE_QUIET") -- cgit v1.2.3-1-g7c22