From b0377343dd8d6f90850bb200f71e18ad13440308 Mon Sep 17 00:00:00 2001 From: Brian Dolbec Date: Mon, 1 Sep 2014 12:32:22 -0700 Subject: [PATCH] chroot-functions.sh: Fix a mis-worded comment Fixes: 900554b0b067e76d3806e520357d91adbfa4fa0c Author: Jorge Manuel B. S. Vicetto (jmbsvicetto) (Mon 19 Dec 2011 11:14:05 PM PST) subject: Make sure portage updates itself at the start of stage1 - thanks to Zac for noticing the issue. --- 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 ce56157e..a31e8bf7 100755 --- a/targets/support/chroot-functions.sh +++ b/targets/support/chroot-functions.sh @@ -169,7 +169,7 @@ setup_pkgmgr(){ # We need to merge our package manager with USE="build" set in case it is # portage to avoid frying our /etc/portage/make.conf file. Otherwise, we could # just let emerge @system could merge it. - # Use --update or portage won't reinstall the same version. + # Use --update or portage might just waste time/cycles and reinstall the same version. [ -e /etc/portage/make.conf ] && echo 'USE="${USE} build"' >> /etc/portage/make.conf run_merge --oneshot --update sys-apps/portage sed -i '/USE="${USE} build"/d' /etc/portage/make.conf -- 2.26.2