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 <davidjames@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
diff --git a/sdk_lib/make_chroot.sh b/sdk_lib/make_chroot.sh
index 3491793..857e47b 100755
--- a/sdk_lib/make_chroot.sh
+++ b/sdk_lib/make_chroot.sh
@@ -409,11 +409,11 @@
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