Each time I merge portage, seem to get loud beeping and a message SHOUTING IN RED occur about the need to replace make.globals, even when there is nothing to replace it with. Reproducible: Sometimes Steps to Reproduce: 1. Only a problem when make.globals does not require updating by user. 2. emerge portage 3. emerge portage Actual Results: 1. on the second emerge, (in fact, on any emerge) get nasty sounds and the following message: * NOTICE: PLEASE *REPLACE* your make.globals. All user changes to variables * in make.globals should be placed in make.conf. DO NOT MODIFY make.globals. * Feature additions are noted in help and make.conf descriptions. Update * them using 'etc-update' please. Maintaining current configs for portage * and other system packages is fairly important for the continued health * of your system. 2. view the file and try to remember changing it - noticing the loud warning at the top...get vague feelings of guilt and culpability. 3. look for the (missing) replacement file /etc/._cfg000_.... 4. panic Expected Results: Only give the message, beep the beeps, etc, when make.globals requires replacing. Preferably this should only be if the file has been changed by the user, as 99.9% of users (the ones with brains) won't have touched the file, so it can be silently replaced. Not a hugely dangerous bug, but important if users get into the habit of ignoring the beeps, etc. Then they will be useless when it really is important. If the file has been modified then the message should include suitable sarcastic comments about modification of a file with # ** DO NOT EDIT THIS FILE ** as the first line. Portage 2.0.49-r13-2 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gentoo-r6_CEAC03) ================================================================= System uname: 2.4.20-gentoo-r6_CEAC03 i686 Celeron (Mendocino) Gentoo Base System version 1.4.3.10 ...deleted the rest
Modified and live.
