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