When using 1.4 rc 3 Live CD to do a new install, I emerge portage as directed by the installation instructions (after setting CONFIG_PROTECT and USE), then unset USE and edit make.conf. I then run the bootstrap script as directed. The first thing the script does is re-emerge portage, which results in my customized version of make.conf being overwritten (because of the CONFIG_PROTECT setting). It seems to me that the bootstrap script should not need to re-emerge portage. Reproducible: Always Steps to Reproduce: 1.emerge portage as per installation instructions 2.edit make.conf 3.run scripts/bootstrap.sh as per instructions Actual Results: portage is immediately re-emerged, which results in my customized make.conf being overwritten with the default version Expected Results: portage did not need to be re-emerged--this would have allowed me to keep my customized version of make.conf
Ran bootstrap script again overnight, and this time everything worked perfectly. I would like to withdraw this bug report, with my apologies for wasting your time.
This was fixed in the ebuild.
