[plug] CVS

[Sol]

Onno Benschop wrote:

>while I'm an experienced developer, I've only been using CVS for a week. 
>
Hey, me too! Well, the bit about using CVS for a week anyway... :-[

>
>Here's what I have:
>
>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.
>
Now coming from me you might want to take this with a barrel of salt 
because it sounds like you have a clue which is more than I can say for 
myself, but, if I understand the principles of CVS correctly and what 
you say you want to do (which is to have all the versions of your 
software represented in CVS) then 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.

Now that might sound labourious, and undoubtedly there's a better way, 
but I think this method might work. It will very likely stuff up your 
versioning system numbers, but you ought to have 18 versions 
represented. I think......

<disclaimer> I was born under a bad sign and was slow at school. If 
anything I suggest goes wrong, don't blame me, blame him.</disclaimer> :-)

Let us know how you fare. Good luck!
sol

>
>
>Here's what I want:
>
>A CVS repository showing the history of my software development.
>
>
>This is what I've tried:
>
>Using cvs import, to import the new version. This works really well and
>all of the files just do their thing, however, it does not remove or
>move any files as they did during the development process. What I end up
>with is a hierarchy that contains all files I've ever used - of course
>they have a history each, but there are files visible in v0.18, that
>were removed in v0.12
>
>I then created a script to manually add/remove files as appropriate, but
>if you remove a file, it's gone, and when you re-add it, it's a new file
>with no history.
>
>I looked at mcvs which promised to do all of the above with no problems,
>however while the software looks like it might work, it doesn't come
>with nearly enough documentation, and it isn't compatible with CVS, so I
>cannot use lincvs to actually develop software.
>
>
>I've found that looking at the history of my code is very enlightning,
>but how do I create a sandbox that only has the files in it that are
>part of v0.x, and not all the others?
>
>
>Here's hoping that one of you uses CVS every day and know how to make
>this work...
>
>Onno Benschop 
>
>Connected via Optus B3 at S15:51'18" - E128:45'05" (Crossing Falls, Kununurra, WA)
>  
>


-- 
==============================
Sol Hanna
solATautonomonDOTnet




_______________________________________________
plug mailing list
plug at plug.linux.org.au
http://mail.plug.linux.org.au/cgi-bin/mailman/listinfo/plug