-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 24/07/12 08:55 PM, Walter Dnes wrote: > On Tue, Jul 24, 2012 at 11:42:31AM +0200, Ralph Sennhauser wrote > >> man 5 portage about files in /etc/portage >> >> make.conf The global custom settings for Portage. See >> make.conf(5). If present, this file will over??? ride settings >> from /etc/make.conf. >> >> >>> 3. This news item is really useful, since the change has a >>> potential to break automated builds. >> >> We aren't discussing dropping support for the old locations here >> but about makeing the new location the default. > > This has the potential to cause problems for people who do things > "the old way", and find that their settings in /etc/make.conf are > not being applied. Instead of a news item, maybe we should be > looking at warnings and/or errors in "emerge"... > > 1) If there is a /etc/make.conf, but no /etc/portage/make.conf, > emerge should generate an ewarn message. Is emerge smart enough to > generate only one ewarn even though it's emerging umpteen > packages?
I'm not sure that this one is particularly necessary, as the default location is not changing according to the package managers. It's only changing according to the stage files that ppl use to install. Once the package managers roll out -expecting- that make.conf should be in /etc/portage/make.conf rather than /etc/make.conf, then yes this should absolutely occur. Right now (and reportedly for the forseeable future) that is not the case. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlAP+ecACgkQ2ugaI38ACPBMQgD/bXuNBSa2s5R7/T1Fb2uZ6cZW +AmYjBjKZDiPMXYYL5sBAJf0mAxgYUETs+KKKk8QS4cTrxK3VvitW1k7yKCEE6zl =YbES -----END PGP SIGNATURE-----
