| 1 |
On Tue, Jul 24, 2012 at 11:42:31AM +0200, Ralph Sennhauser wrote |
| 2 |
|
| 3 |
> man 5 portage about files in /etc/portage |
| 4 |
> |
| 5 |
> make.conf |
| 6 |
> The global custom settings for Portage. See make.conf(5). If |
| 7 |
> present, this file will over??? ride settings from /etc/make.conf. |
| 8 |
> |
| 9 |
> |
| 10 |
> > 3. This news item is really useful, since the change has a potential |
| 11 |
> > to break automated builds. |
| 12 |
> |
| 13 |
> We aren't discussing dropping support for the old locations here but |
| 14 |
> about makeing the new location the default. |
| 15 |
|
| 16 |
This has the potential to cause problems for people who do things "the |
| 17 |
old way", and find that their settings in /etc/make.conf are not being |
| 18 |
applied. Instead of a news item, maybe we should be looking at warnings |
| 19 |
and/or errors in "emerge"... |
| 20 |
|
| 21 |
1) If there is a /etc/make.conf, but no /etc/portage/make.conf, emerge |
| 22 |
should generate an ewarn message. Is emerge smart enough to generate |
| 23 |
only one ewarn even though it's emerging umpteen packages? |
| 24 |
|
| 25 |
2) If there is a /etc/make.conf *AND* a /etc/portage/make.conf, emerge |
| 26 |
should halt immediately with an error message. If a user has made a |
| 27 |
/etc/make.conf, they will probably expect it to take effect, which is |
| 28 |
not what's going to happen. This will save the user forums from being |
| 29 |
hit with the same question over and over about settings in /etc/make.conf |
| 30 |
being ignored. |
| 31 |
|
| 32 |
3) When support for /etc/make.conf is finally dropped, the presence of |
| 33 |
/etc/make.conf should make emerge halt immediately with an error message. |
| 34 |
|
| 35 |
-- |
| 36 |
Walter Dnes <waltdnes@××××××××.org> |
Archives