Simon 'corecode' Schubert <[EMAIL PROTECTED]> wrote: > Johannes Hofmann wrote: >> Matthias Schmidt <[EMAIL PROTECTED]> wrote: >>> Hi, >>> >>> * Matthew Dillon wrote: >>>> Use the defaults mechanism. /etc/<blah> overriides >>>> /etc/defaults/<blah>. >>>> /etc/defaults/<blah> is owned by the build system, /etc/<blah> is owned >>>> by the user. >>> This is fine for system config files containing a lot of entries. If we >>> start to introduce this for every daemon/$whatever we end up with a >>> mess of default files. I agree with Simon and would vote for a more >>> sophisticated solution which involves merging the differences or >>> something similar to that. >> >> I like the simple /etc/defaults/ mechanism a lot. It works and is easy to >> understand. Why do you think more files in /etc/defaults/ would create a >> mess? >> I'd say it's much cleaner than any automated config file merging. > > Because you'd have to modify every single program to read defaults from > one place and overrides from another. Most programs/configs don't work > this way.
Ok that's for existing programs. For those one could perhaps create the actual config file from both, the system provided file in /etc/defaults/ and the user provided file in /etc/? That would avoid having files that are touched by the system and the user. Cheers, Johannes
