On Wed, 6 Sep 2006, Alexander Wirt wrote:
Joerg Lehmann schrieb am Dienstag, den 05. September 2006:
Hi Dag, hi Alex,
On 04.09.06, Dag Wieers wrote:
PS I also believed it may have been caused by my config-file being overwritten after doing the install, which is still a major issue for me as it bites me every new release I tried. I now hardlink the configfile :)
I still don't fully understand the problem. Why do you change the global config file (in /etc) at all, except for distribution purposes? And in the latter case, there should be no problem anyway. The right place to configure PyTone is in ~/.pytone/pytonerc which will never be overwritten.
Well, the global config-file contains the configuration of the sound output and some other configuration options I consider 'global' (specific to the system).
I would have no problem removing the file from the setup.py file. Probably for you packagers this doesn't make a difference, anyway.
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.
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.
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]