[plug] CVS

[Bernard Blackham]

On Sun, Sep 14, 2003 at 06:49:06PM +0800, Sol wrote:
> >A directory with software that I wrote. Each version of the software is
> >in its own directory, eg. v0.1, v0.2, etc, all told 18 versions.

> I think that the best way to do it would be:
> 1) establish the CVSROOT in (a copied directory) of your v0.1 code. 
> Import this, NOT the whole directory with 18 versions. Just the 0.1 
> files/directory.
> 2) Then do a commit.
> 3) Then check out the 0.1 files into a working directory and replace the 
> files in that directory with the 0.2 files.
> 4) Check the files in the working directory into CVS and do another commit.
> 5) Repeat steps 2-4 18 times.

This would be how I would do it, with an extra step (see below).
I've been using CVS for a while, but I can't claim to know it inside
out.

> Now that might sound labourious, and undoubtedly there's a better way, 

It could be scripted ... :)

> It will very likely stuff up your versioning system numbers, but
> you ought to have 18 versions represented.

You can specify a symbolic tag for any stage in the repository - so
after each step, you could run "cvs tag 0_1_RELEASE" (with the right
version number). And do likewise each time you create a released
tarball.

Then later you can checkout each revision by specifying "-r
0_1_RELEASE" etc. I think there might be some convention to tag
names for released versions, but I don't know what it is and it's
probably not critical - so long as it makes sense to the people that
will potentially use them :)

HTH,

Bernard.

-- 
 Bernard Blackham 
 bernard at blackham dot com dot au
_______________________________________________
plug mailing list
plug at plug.linux.org.au
http://mail.plug.linux.org.au/cgi-bin/mailman/listinfo/plug