From f23b1243fc6ee43612633723ff2d0d92870bce51 Mon Sep 17 00:00:00 2001 From: "Jorge Manuel B. S. Vicetto (jmbsvicetto)" Date: Tue, 20 Dec 2011 06:09:24 -0100 Subject: Make sure portage updates itself at the start of stage1 - thanks to Zac for noticing the issue. --- targets/support/chroot-functions.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/targets/support/chroot-functions.sh b/targets/support/chroot-functions.sh index c454aaf1..af693e8c 100644 --- a/targets/support/chroot-functions.sh +++ b/targets/support/chroot-functions.sh @@ -165,8 +165,9 @@ setup_pkgmgr(){ # We need to merge our package manager with USE="build" set in case it is # portage to avoid frying our /etc/make.conf file. Otherwise, we could # just let emerge system could merge it. + # Use --update or portage won't reinstall the same version. [ -e /etc/make.conf ] && echo 'USE="${USE} build"' >> /etc/make.conf - run_merge --oneshot --nodeps sys-apps/portage + run_merge --oneshot --nodeps --update sys-apps/portage sed -i '/USE="${USE} build"/d' /etc/make.conf } -- cgit v1.2.3-18-g5258