Fixes: 900554b0b067e76d3806e520357d91adbfa4fa0c
Author: Jorge Manuel B. S. Vicetto (jmbsvicetto) <[email protected]> (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 ce56157..3495f14 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 will 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
