During execution of the /usr/portage/scripts/bootstrap.sh script, it seems necessary to modify the options in make.conf. At present this is done by renaming the user's make.conf to make.conf.build, then creating a new make.conf with the required options. At the end of the script make.conf.build is moved back to make.conf. If all goes well, this works very smoothly. Unfortunately, the sript may fail for any of a large number of reasons, and then the final rename may be skipped. If the hapless user forgets to check, fixes the immediate problem, and retarts the script the carefully-crafted user make.conf is lost in a second rename cycle. I've had this happen several times, and while it is not a disaster it can waste a lot of time. The sad fact is that trapping the need for a reverse rename on script failure is no simple task. If emerge could take a switch to accept configuration info from a different file, for example emerge --config /etc/make.conf.boot ... The rather clumsy rename could be avoided, and cleanup would never be an issue. This would enable a much more friendly bootstrap process. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Hrrrmn... I think bootstrap.sh is actually covered by base-system. The livecd herd only covers the actual LiveCD. It seems your issue is with the bootstrap.sh, or possibly even portage itself. I'm going to reassign to bug-wranglers and let them figure out where this should go.
bootstrap.sh now cleans up after itself by moving the make.conf.build back to make.conf upon error/termination/etc...
Moving these so we can remove the "Install CD" component from "Gentoo Linux". I apologize to everyone for this spam, but according to the bugzilla developers, this is the only reasonable way to do this.
