1 |
On Wed, May 16, 2012 at 11:36 AM, Eray Aslan <eras@g.o> wrote: |
2 |
> On 2012-05-16 12:13 PM, Andreas K. Huettel wrote: |
3 |
>>>> make.conf(5) man page: |
4 |
>>>> This causes the CONFIG_PROTECT behavior to be skipped for files that |
5 |
>>>> have not been modified since they were installed. |
6 |
>> |
7 |
>> +1 very good idea |
8 |
> |
9 |
> Hmm, does that mean that when a default changes in (or some new setting |
10 |
> is added to) an app config file, I'll get no prompt and no warning |
11 |
> assuming I go with the default settings in the app? That presumes that |
12 |
> the new default or the new setting does not break my setup. That is a |
13 |
> big assumption. |
14 |
|
15 |
Generally, several PMS (I think apt does it as well) make this assumption: |
16 |
if config file C owned by package P has never been modified, meaning |
17 |
that md5 or whatever is the same, the old C of P was fine, so is the |
18 |
new C. |
19 |
On the other hand, if the old C has been modified, then the above |
20 |
assumption is not valid. |
21 |
|
22 |
This also helps a lot in the scenario where critical configuration |
23 |
files are not updated before reboot, which might result in an |
24 |
unbootable system (ouch!). |
25 |
|
26 |
> |
27 |
> Even if we go with enabling it by default, please have a news item so |
28 |
> that one can turn it off if necessary. Even then, new installs will |
29 |
> have to remember to turn it off. |
30 |
> |
31 |
> -- |
32 |
> Eray Aslan <eras@g.o> |
33 |
> |
34 |
|
35 |
|
36 |
|
37 |
-- |
38 |
Fabio Erculiani |