[gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-15 Thread Duncan
Zac Medico posted on Tue, 15 May 2012 15:24:53 -0700 as excerpted: > Hi, > > In case you aren't familiar with it, here's the description from the > make.conf(5) man page: > > This causes the CONFIG_PROTECT behavior to be skipped for files that > have not been modified since they were install

Re: [gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-16 Thread Fabio Erculiani
I implemented this feature in Entropy long time ago (2009 iirc) and enabled it by default as well. We never had a single issue. Users seem quite happy about it. So yeah, go for it! -- Fabio Erculiani

Re: [gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-16 Thread Andreas K. Huettel
> > 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 > The best thing about it is not having to worry about missing an important > change in a file I DO change, due to all th

Re: [gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-16 Thread Eray Aslan
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 set

Re: [gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-16 Thread Fabian Groffen
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

Re: [gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-16 Thread Pacho Ramos
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 bee

Re: [gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-16 Thread Fabio Erculiani
On Wed, May 16, 2012 at 11:36 AM, 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,

Re: [gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-16 Thread Eray Aslan
On 2012-05-16 12:56 PM, Fabio Erculiani wrote: > Generally, several PMS (I think apt does it as well) make this assumption: > if config file C owned by package P has never been modified, meaning > that md5 or whatever is the same, the old C of P was fine, so is the > new C. Yep, and I always thoug

Re: [gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-16 Thread Fabian Groffen
On 16-05-2012 11:48:20 +0200, Pacho Ramos wrote: > 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 b

Re: [gentoo-dev] Re: RFC: Enable FEATURES=config-protect-if-modified by default?

2012-05-16 Thread Rich Freeman
On Wed, May 16, 2012 at 5:02 AM, Fabio Erculiani wrote: > I implemented this feature in Entropy long time ago (2009 iirc) and > enabled it by default as well. > We never had a single issue. Users seem quite happy about it. > This is also the default behavior with the cfg-update alternative to dis