Re: [gentoo-portage-dev] How to prevent dispatch-conf from reverting valid changes

[Pacho Ramos <pacho@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

El jue, 27-09-2012 a las 13:21 -0700, Zac Medico escribió:
> On 09/27/2012 01:16 PM, Pacho Ramos wrote:
> > El dom, 23-09-2012 a las 11:06 -0700, Zac Medico escribió:
> >> On 09/23/2012 03:59 AM, Pacho Ramos wrote:
> >>> This looks like could be done with:
> >>> # Automerge files comprising only whitespace and/or comments
> >>> # (yes or no)
> >>> replace-wscomments=no
> >>>
> >>> , setting it to "yes" in dispatch-conf.conf
> >>
> >> It seems like that option is only likely to benefit people who have
> >> disabled the default config-protect-if-modified FEATURES setting, and
> >> I'm not sure that it's a good idea to hide "trivial" differences from
> >> these people by default.
> > 
> > Would be a way to detect changes like "0" to "1" or "false" -> "true",
> > "yes" -> "no"... ? I think they usually shouldn't be changed :|
> 
> I'm not sure what "problem" you're trying to solve. Since enabling
> FEATURES=config-protect-if-modified, I've found the volume of config
> updates to be much more manageable, and the configs that I do have to
> merge manually don't really bother me.

Well, I hit the problem when updating from stable openrc to 0.10.5 and
needing to reedit some config files as, as normal, I had uncommented
some options, modified some defaults... (like keymap, clock settings...)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]