1 |
Jeff Kowing said: |
2 |
> |
3 |
> I was interested in any methods or techniques that gentoo folks have found |
4 |
> useful in helping to manage their /etc configuration files. |
5 |
|
6 |
etc-update |
7 |
|
8 |
> |
9 |
> One particular problem I have is when I do an update that affects lots of |
10 |
> /etc files. After the emerge I have lots of ._cfg* files to go through. |
11 |
> I know there is no magical method, but I was |
12 |
> looking for some way to do something like the following: |
13 |
> |
14 |
> 1. Auto replace all /etc files that I have not personally modified |
15 |
> with the new ._cfg* file. |
16 |
> |
17 |
> 2. Do the usual ._cfg* thing when I have previously modified the |
18 |
> original /etc file. Then, as normal, at my convenience I can use |
19 |
> etc-update and/or my favorite merge tool to take care of those. |
20 |
> |
21 |
> I know there are merge tools that could detect this sort of thing |
22 |
> based upon the ancestor version of the /etc file. Or, I imagine there are |
23 |
> fairly straight forward ways to make a list before the emerge of which |
24 |
> /etc/ files have been modified and and which have not. That list could |
25 |
> then be used by another script after the emerge to decide which /etc files |
26 |
> may be automatically replaced. |
27 |
> |
28 |
> But before I try doing this sort of thing, maybe someone already has done |
29 |
> this? |
30 |
> |
31 |
> (By the way, I know about CONFIG_PROTECT and CONFIG_PROTECT_MASK, but, I |
32 |
> don't really see how they could achieve what I'm looking for. |
33 |
> Besides, I believe they only operate on directories rather than |
34 |
> invidual files). |
35 |
> |
36 |
> Thanks for any advice. |
37 |
> |
38 |
> -- |
39 |
> Jeff Kowing |
40 |
> jeffrey.d.kowing@××××.gov |
41 |
> |
42 |
> -- |
43 |
> gentoo-dev@g.o mailing list |
44 |
|
45 |
|
46 |
|
47 |
|
48 |
-- |
49 |
gentoo-dev@g.o mailing list |