From 66fd81f9529904e238b8cabc2be860c2c4bd5a92 Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Tue, 28 Feb 2012 13:13:20 -0500 Subject: [PATCH] make_chroot: use --quiet when doing initial update There's no reason to always show the full build output when updating the chroot, so use the --quiet flag. If there is a failure, emerge will dump the full log like normal. BUG=None TEST=`cros_sdk --delete && cros_sdk` showed much less output Change-Id: I062900325d0005db150dbd1267048a7c19df2ac5 Reviewed-on: https://gerrit.chromium.org/gerrit/16977 Reviewed-by: David James Reviewed-by: Brian Harring Commit-Ready: Mike Frysinger Tested-by: Mike Frysinger --- sdk_lib/make_chroot.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sdk_lib/make_chroot.sh b/sdk_lib/make_chroot.sh index 34917935e3..857e47b97c 100755 --- a/sdk_lib/make_chroot.sh +++ b/sdk_lib/make_chroot.sh @@ -409,11 +409,11 @@ fi sudo sh -c "echo STAGE3=$STAGE3 > $CHROOT_STATE" info "Updating portage" -early_enter_chroot emerge -uNv portage +early_enter_chroot emerge -uNv --quiet portage info "Updating toolchain" -early_enter_chroot emerge -uNv $USEPKG '>=sys-devel/gcc-4.4' sys-libs/glibc \ - sys-devel/binutils sys-kernel/linux-headers +early_enter_chroot emerge -uNv --quiet $USEPKG '>=sys-devel/gcc-4.4' \ + sys-libs/glibc sys-devel/binutils sys-kernel/linux-headers # HACK: Select the latest toolchain. We're assuming that when this is # ran, the chroot has no experimental versions of new toolchains, just