This is the script that I use to update amaroK from cvs.

[code:1]
#!/bin/bash

echo \"Updating Amarok SVN\"
cd /home/ben/multimedia/
sudo pwd
svn up amarok/
./configure --enable-mysql
unsermake
sudo unsermake install
[/code:1]

It has the pwd in there so I can put in my password when the script starts and not have to wait until the install.

The script works fine for a couple of days but eventually it will stop during the make process and ask if I want to override an error 644 or something like that. From what I have learnt an error 644 results from the wrong permissions in the files.

Does anyone know why it is doing this? I usually just delete the whole amarok source and start again until the next time it happens. It may be something to do with unsermake as it never used to happen when I used a similar script using regular make.

Use this script instead, it\'s the official one; tested and recommended.

http://kde-apps.org/content/show.php?content=27313

Great, thanks.

I\'ve started using the official script and it is great, an order of magnitude better than my half blind effort.

Does anyone know how I make it a cron job? So far I set the working directory in the script to the usual and then I put a copy of the script in /etc/cron.daily. Is this all I have to do? I have left it for over 24 hours so far and the files don\'t seem to have been updated (maybe I am just impatient).

Keep up the fantastic work, amaroK just keeps getting better and better. New features like the use of libgpod are just the icing on the cake: I\'ve finally been able to stop using gtkpod.

Thanks for the player and hopefully for the advice.