| 1 |
On 08/01/2012 08:33 AM, Duncan wrote: |
| 2 |
> Pacho Ramos posted on Wed, 01 Aug 2012 12:19:20 +0200 as excerpted: |
| 3 |
> |
| 4 |
>> On every openrc update I get dispatch-conf wanting to revert all my |
| 5 |
>> changes in /etc/conf.d files, like KEYMAP, clock... |
| 6 |
>> |
| 7 |
>> Is there any way to prevent it from doing that? |
| 8 |
>> |
| 9 |
>> Thanks a lot for the info |
| 10 |
> |
| 11 |
> Interesting. I use etc-update here, and at least it (working with |
| 12 |
> portage) has a feature such that it takes the hash of the package's config |
| 13 |
> file, and as long as that doesn't change, it won't bother you again. |
| 14 |
|
| 15 |
This is actually a feature of portage's merge code, which can be |
| 16 |
disabled by the emerge --noconfmem option. |
| 17 |
|
| 18 |
> Of course if there's a change in the package's config file, it simply |
| 19 |
> diffs the files, thus returning hits for parts of the files that haven't |
| 20 |
> changed since the last time if they differ, because some other chunk of |
| 21 |
> the file is new (say one entirely new option in a file of dozens, the |
| 22 |
> rest of which haven't changed). |
| 23 |
|
| 24 |
Unlike etc-update, dispatch-conf uses diff3. |
| 25 |
|
| 26 |
-- |
| 27 |
Thanks, |
| 28 |
Zac |
Archives