On Tue, 5 Sep 2006, Joerg Lehmann wrote:
On 04.09.06, Dag Wieers wrote:
Anyway, the attached patch should fix this. It will be included in the next version, but you can easily include it in your packages.
That was quick :)
I already had it in Subversion as it did bite me as well on an Intel machine. Strangely enough the unfixed version worked with an emu10k1 card on another little-endian machine.
Anyway, it would be good if you could include this patch in your packages as it could be a bit of a show-stopper for many people.
Ok, can you say what revisions we need ? diff -r oldrev:newrev http://path-to-svn/ subversion is great for pointing people to patches without having to produce them ;-)
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.
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 :) 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]