In the Portage ebuild: use build && [ -f /etc/make.conf ] && rm -f ${D}/etc/make.conf This has the unintended consequence of breaking stage building. Stages are left without a make.conf in the end, which causes things like the initial `emerge sync` to fail (as well as env-update). We fixed this problem manually for rc4, but a less temporary solution would be optimal.
Ummmm... Is this supposed to be against the old code? Note the middle portion of that line. If make.conf exists, then the new make.conf isn't deleted... Conversely... It only replaces the conf when !build and it doesn't already exist. The problem has been fixed, I do believe.
