| 1 |
On 8/30/05, Jerry Turba <jturba@×××××××.com> wrote: |
| 2 |
> As I understand the process etc-update lists new configuration files |
| 3 |
> provided by the program authors. I have tried to define some rules for |
| 4 |
> myself to determine how to handle these new files. |
| 5 |
> |
| 6 |
> 1. If I made a change to a file I will never allow the new config file |
| 7 |
> to overwrite the old file. |
| 8 |
|
| 9 |
I know one person who operated like this but I didn't agree. I think |
| 10 |
that you have to (eventually) do the update. The developers change |
| 11 |
things in these files also. If you don't change you don't get the |
| 12 |
updates, or things (possibly) don't get activated. |
| 13 |
|
| 14 |
> |
| 15 |
> 2. If the new config file is a new default file I will accept the new file. |
| 16 |
> |
| 17 |
> 3. I will never change a file that is program code, (I am not a programmer). |
| 18 |
> |
| 19 |
> Are these rules sane? What kind of problems could I run into doing this? |
| 20 |
> What would be some better rules to use? I have tried dispatch-conf but I |
| 21 |
> still have to make the same decisions. Am I missing something? |
| 22 |
> |
| 23 |
|
| 24 |
My rules are: |
| 25 |
|
| 26 |
1) The update was put there for a reason. |
| 27 |
|
| 28 |
2) If it's a file in /etc/initd then I update it automatically. |
| 29 |
|
| 30 |
3) If it's a file in /etc/conf.d then I update it very carefully. |
| 31 |
|
| 32 |
4) If it's a file in /etc/, /etc/X11, or elsewhere the I update it |
| 33 |
very carefully but possibly not right now. |
| 34 |
|
| 35 |
5) Anything else, I go slow. Maybe I look for messages from others on |
| 36 |
this list having problems before I do something. |
| 37 |
|
| 38 |
My experience is that rules 2 & 3 account for 80-90% of the updates. |
| 39 |
|
| 40 |
Cheers, |
| 41 |
Mark |
| 42 |
|
| 43 |
-- |
| 44 |
gentoo-user@g.o mailing list |
Archives