| 1 |
El jue, 27-09-2012 a las 13:21 -0700, Zac Medico escribió: |
| 2 |
> On 09/27/2012 01:16 PM, Pacho Ramos wrote: |
| 3 |
> > El dom, 23-09-2012 a las 11:06 -0700, Zac Medico escribió: |
| 4 |
> >> On 09/23/2012 03:59 AM, Pacho Ramos wrote: |
| 5 |
> >>> This looks like could be done with: |
| 6 |
> >>> # Automerge files comprising only whitespace and/or comments |
| 7 |
> >>> # (yes or no) |
| 8 |
> >>> replace-wscomments=no |
| 9 |
> >>> |
| 10 |
> >>> , setting it to "yes" in dispatch-conf.conf |
| 11 |
> >> |
| 12 |
> >> It seems like that option is only likely to benefit people who have |
| 13 |
> >> disabled the default config-protect-if-modified FEATURES setting, and |
| 14 |
> >> I'm not sure that it's a good idea to hide "trivial" differences from |
| 15 |
> >> these people by default. |
| 16 |
> > |
| 17 |
> > Would be a way to detect changes like "0" to "1" or "false" -> "true", |
| 18 |
> > "yes" -> "no"... ? I think they usually shouldn't be changed :| |
| 19 |
> |
| 20 |
> I'm not sure what "problem" you're trying to solve. Since enabling |
| 21 |
> FEATURES=config-protect-if-modified, I've found the volume of config |
| 22 |
> updates to be much more manageable, and the configs that I do have to |
| 23 |
> merge manually don't really bother me. |
| 24 |
|
| 25 |
Well, I hit the problem when updating from stable openrc to 0.10.5 and |
| 26 |
needing to reedit some config files as, as normal, I had uncommented |
| 27 |
some options, modified some defaults... (like keymap, clock settings...) |
Archives