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