* Joerg Lehmann <joerg@luga.de> [2006-09-05 13:00]:
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.
For me that is an improvement. Of course packagers then need to put it in place themselves. But every existing package definition will complain as it does not find the expected file. So it does not need direct communication. Packagers will understand what they need to do :)
Ok, so I'll remove this file in the future.
Jörg
And what about new config-options? How are they communicated then? With 2.3.1 there came new keys for rating for example ... I always used the diff from the new pytonerc to look if there is something new I should know about ;-) @Dag: I have for every version of pytone a pytonerc in /etc and a link to the currently used. Before every update I remove the link ... simple as that ;-) Luckily the whole problem does not exist in Gentoo since the files in /etc are protected and run through a diff-proces anyway. Just my thoughts Stefan ========================================================= My very personal wishlist for Pytone - just ignore it ;-) ========================================================= * BPS recognition Show the bits per seconds from a song in the MP3 info window * Pause between tracks * Some sort of replaygain * Extended search function -- Stefan Wimmer <swimmer@xs4all.nl>