>I'm not certain that it's necessary, but I always stop the Windows >service before performing a SVN update. This can be conveniently done >from slimtray, then start SlimServer up again afterwards. Prior to >doing this, I'd often get an error while doing the update, as >TortoiseSVN was unable to overwrite a file - usually the main >slimserver.pl file. > I haven't experienced that problem yet.
I wrote a batch script that does an SVN update, shows the log, stops the service and starts it again. Perhaps I should change it to stop the service then perform the update. The log seems to by default show changes that have been committed during the current day. It would be nice if there was a way of identifying the current svn number, update SVN, get the new svn number, then show the log for changes between the two versions. I guess there are SVN commands to do this - I need to have a play. I had been meaning to set up SVN for a while, as I was interested in having a look around the code with an aim to being able to participate a bit more with bug investigations and patches. My perl knowledge is a little limited, so getting SVN set up seemed like a logical starting point - at least I can see changes made to fix bugs and try to understand how they work. Phil _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
