The main cvs trunk for scoop is now the development branch (code named 0.7, spiffy, eh? :). Off of the development branch is the 0.6 stable branch, labeled scoop-0_6-stable in cvs (since cvs doesn't let you include '.' in labels, we change the '.' to a '_').
When we get to release 0.8, ( the next stable release ) we'll branch off another stable branch. Now how do you use this new found knowledge or avoid having it affect you?
First you need to know what version you are running. Check the VERSION file in the root directory of scoop. Now if you're not running
cvs or 0.6 as of the posting of this story, its not there. If you don't have it, then you're running pre-0.6 :-) If you do have it, check the line in that VERSION file that has $scoop_env{Version}
Thats where the
version is set. It will be either scoop-0_7-dev or scoop-0_6-stable.
Now, what about upgrading to get the latest patches and/or features? Well,
cvs knows what version you are currently running, so if you want to keep running
that same version, then just upgrade as before.
me@myhost ~/scoop$ cvs login
Password:
me@myhost ~/scoop$ cvs update
...cvs output...
me@myhost ~/scoop$
But what if you want to get a different version than the one you are running? Well here is a quick summary of all of the cvs commands to switch from tree to tree or from stable to development etc. (Note: All of these commands assume you did a cvs login first)
To access the stable branch:
cvs update -r scoop-0_6-stable # from scoop/
cvs checkout -r scoop-0_6-stable scoop # from scoop/../
To get to the main cvs trunk (i.e. the dev code):
cvs update -A # from scoop/
cvs checkout -A scoop # from scoop/../
So thats all there is to the cvs stuff. That should help you track the tree that you want, easily.
Now this is where I'd put in the change list, but so much has changed since oh so long ago with .6-pre2 :-) So go grab scoop-0.6 from sourceforge, I'll have a link in the box on the left of the main page soon. Oh yeah, and if you are running a .6-pre2 version of scoop, you will need to make some minor changes to your httpd.conf. If you don't make the changes, it won't affect anything, but it will be handy for tracking what version you are
running without having to log into your server