Dag Wieers schrieb am Mittwoch, den 06. September 2006:
*snip*
Maybe it would be good to allow a include, like /etc/pytone/pytonerc and /etc/pytone/pytonerc.local, so that users can add their changes to the local file and distributions can just overwrite the global config. This works good for packages like bind in Debian.
But, what would go into the default /etc/pytone/pytonerc that no-one should really need to change ? The current one is not sufficient because what I need to change on a global scale is the audio device configuration and the look and feel.
Ah no, thats not directly what I meaned, that file should be empty by default and should be processed after the normal config, but before the user config. If a user wants to change something global he would enter only the changed variable into the .local file. Not more, so the global wouldn't get changed anymore.
Personally, what I do is put the default configuration file as part of the documentation as a reference. And this file is always overwritten upon installation of the package, not the real configuration file.
Includes won't fix the problem we currently have with overwriting configuration files.
This won't happen on debian, if you changed the global config, the user will be asked if he wants to overwrite his config.
Alex