1 |
On Sunday 12 February 2006 07:37, Maarten <gentoo@××××××××.org> wrote about |
2 |
'[gentoo-user] Handling of config updates, RFC': |
3 |
> What tickles me the most about the current process is that one sometimes |
4 |
> gets huge lists of updated files by updating a single package. A package |
5 |
> which may have never been used, or at least configured, by the user. |
6 |
> For instance, updating webmin, or snort, yields many many ._cfg files an |
7 |
> average user knows little about, and does not care about since he never |
8 |
> tweaked them. In other words, they are in their distibution-default |
9 |
> state, never edited. It stands to reason everyone would want all those |
10 |
> files overwritten by the new ones, is it not ? Well, neither tool does |
11 |
> that now. |
12 |
|
13 |
1) "The Gentoo Way" says that gentoo shouldn't make that decision for you. |
14 |
|
15 |
2) Check out your /etc/dispatch-conf.conf; It has options to automatically |
16 |
perform a number of merges and even keep an RCS history of config files to |
17 |
ensure that it is easy to rollback in breaking changes. I tell |
18 |
dispatch-conf to automatically merge config files I haven't touched. |
19 |
|
20 |
I'd say the tools provided with portage, plus cfg-update, as mentioned by |
21 |
the other poster, as more than capable for my use (actually, the only one |
22 |
I /ever/ use is dispatch-conf). Before trying to stir up development |
23 |
efforts on another method, please try and fully understand the tools |
24 |
gentoo provides. I'm not saying config file maintainence couldn't be |
25 |
improved in gentoo, but I think it's in a state that satisfied the |
26 |
majority of users and (more importantly) developers. It does help to |
27 |
tweak your CONFIG_PROTECT and CONFIG_PROTECT_MASK. |
28 |
|
29 |
-- |
30 |
Boyd Stephen Smith Jr. |
31 |
bss03@××××××××××.com |
32 |
ICQ: 514984 YM/AIM: DaTwinkDaddy |
33 |
-- |
34 |
gentoo-user@g.o mailing list |