El mié, 16-05-2012 a las 11:42 +0200, Fabian Groffen escribió:
> On 16-05-2012 12:36:03 +0300, Eray Aslan wrote:
> > On 2012-05-16 12:13 PM, Andreas K. Huettel wrote:
> > >>> make.conf(5) man page:
> > >>> This causes the CONFIG_PROTECT behavior to be skipped for files that
> > >>> have not been modified since they were installed.
> > >
> > > +1 very good idea
> > Hmm, does that mean that when a default changes in (or some new setting
> > is added to) an app config file, I'll get no prompt and no warning
> > assuming I go with the default settings in the app? That presumes that
> > the new default or the new setting does not break my setup. That is a
> > big assumption.
> I'd think so, yes
But similar assumption applies to current behavior: if a user forgets to
run dispatch-conf after updating and machine is rebooted (by error, due
some power failure, due other users rebooting it...), they will probably
get failures when booting and, for example, some init.d scripts file to
start due obsolete conf.d files being preserved by default.
> > Even if we go with enabling it by default, please have a news item so
> > that one can turn it off if necessary. Even then, new installs will
> > have to remember to turn it off.
But I also agree with releasing a news item for the change of course :)