Hi PyToners,
I finally got around to do some little PyTone work. Since there were some complaints about the huge disk space consumed during the song db upgrade, I now added an alternative, non-atomic database upgrade code and prompt the user before an upgrade. This is contained in the next prerelease, which can be found here:
http://www.luga.de/pytone/download/PyTone-2.3.0-pre2.tar.gz
If you still have an old database lying around, please give it a try - as always, I would really appreciate feedback on this change.
Jörg
On Thu, 8 Sep 2005, Joerg Lehmann wrote:
I finally got around to do some little PyTone work. Since there were some complaints about the huge disk space consumed during the song db upgrade, I now added an alternative, non-atomic database upgrade code and prompt the user before an upgrade. This is contained in the next prerelease, which can be found here:
http://www.luga.de/pytone/download/PyTone-2.3.0-pre2.tar.gz
If you still have an old database lying around, please give it a try - as always, I would really appreciate feedback on this change.
After installing it from subversion:
+ My config file was once again overwritten + It didn't start:
[dag@emyn ~]$ pytone python: can't open file 'src/pytone.py'
[dag@emyn ~]$ cat /usr/bin/pytone #!/bin/sh python src/pytone.py "$@"
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]
Hi Dag!
On 10.09.05, Dag Wieers wrote:
I finally got around to do some little PyTone work. Since there were some complaints about the huge disk space consumed during the song db upgrade, I now added an alternative, non-atomic database upgrade code and prompt the user before an upgrade. This is contained in the next prerelease, which can be found here:
http://www.luga.de/pytone/download/PyTone-2.3.0-pre2.tar.gz
If you still have an old database lying around, please give it a try - as always, I would really appreciate feedback on this change.
After installing it from subversion:
Did you run "python setup.py install"? This is currently not recommended.
- My config file was once again overwritten
You mean the site-wide config file /etc/pytonerc? If yes, that's how distutils works.
It didn't start:
[dag@emyn ~]$ pytone python: can't open file 'src/pytone.py'
[dag@emyn ~]$ cat /usr/bin/pytone #!/bin/sh python src/pytone.py "$@"
Yup, currently everything only works automatically, if you run PyTone from the original directory. One would need to replace the install_scripts routines to update the files correspondingly. Unfortunately, there is no simpler solution.
Jörg
* Dag Wieers dag@wieers.com [2005-09-10 03:32]:
After installing it from subversion:
My config file was once again overwritten
It didn't start:
[dag@emyn ~]$ pytone python: can't open file 'src/pytone.py'
[dag@emyn ~]$ cat /usr/bin/pytone #!/bin/sh python src/pytone.py "$@"
If you are - by any chance - using Gentoo as your distribution you could use this ebuild:
http://www.xs4all.nl/~swimmer/music/PyTone-2.3.0-r2.ebuild
to install PyTone and to avoid those little annoying things ;-)
And it would help me if I could get any feedback to find other annoying little things which are coming up by using an ebuild to install it :)
So feel free to download and test it and give me feedback that I can finally present this fantastic tool to the Gentoo community!
Greetz 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
* Modifiable playlists Modify/delete playlists
* Pause between tracks
* Some sort of replaygain
* Extended search function (any thoughts already?) -- Stefan Wimmer swimmer@xs4all.nl
On Thu, 8 Sep 2005, Joerg Lehmann wrote:
I finally got around to do some little PyTone work. Since there were some complaints about the huge disk space consumed during the song db upgrade, I now added an alternative, non-atomic database upgrade code and prompt the user before an upgrade. This is contained in the next prerelease, which can be found here:
http://www.luga.de/pytone/download/PyTone-2.3.0-pre2.tar.gz
If you still have an old database lying around, please give it a try - as always, I would really appreciate feedback on this change.
It worked very well on my laptop and I would make it the default method. Why would it need to be atomic ? Can't we perform the upgrade on a copy and if everything is ok, move it back (atomic) ?
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]
Hi Dag!
On 10.09.05, Dag Wieers wrote:
I finally got around to do some little PyTone work. Since there were some complaints about the huge disk space consumed during the song db upgrade, I now added an alternative, non-atomic database upgrade code and prompt the user before an upgrade. This is contained in the next prerelease, which can be found here:
http://www.luga.de/pytone/download/PyTone-2.3.0-pre2.tar.gz
If you still have an old database lying around, please give it a try - as always, I would really appreciate feedback on this change.
It worked very well on my laptop and I would make it the default method. Why would it need to be atomic ? Can't we perform the upgrade on a copy and if everything is ok, move it back (atomic) ?
I will have a look into this (it requires copying the database and the last log file (?)), but for the moment I'm happy with this solution. Hopefully, database scheme upgrades are not happening that often anyway.
Jörg