Re: Setting up CVS

[Fabian Cenedese]

>  Indeed, unfortunately I'm the new guy, and it's a small setup, and they've 
> just been throwing stuff together for the past 30 years or so, simply to get 
> it to work in the easiest way possible with the least amount of effort... It 
> started as an accounting firm, and then a computer programmer or two came 
> along... so I'm not to terribly happy with the setup. And I'm just a little 
> intern, soooo I'm just trying to improve things a bit and only have a slight 
> clue as to what I'm doing really... so I've spent most of my time reading 
> through quite a bit of documentation and just doing research on ways for 
> Source Code Management and other ways to improve security and the overall 
> setup at work... But now my brain hurts and I'm off work, so I'm going to 
> relax for a bit and come back for a bit more research... Thanks for the 
> input. It's greatly appreciated.

If possible use a WinNT+ machine as server so you can use cvsNT as service.
(or even a linux machine, doesn't have to be powerful :)
If not available you need to have a shared drive. cvs can cause problems on
that, read in the mailing archives. But as you're Windows only it might work
well.
Then you need a client, be it the pure command line cvs or some GUI like
WinCVS. After setting up the repository (on command line with simple
'cvs init S:\RepoPath' (S like shared drive, RepoPath what you like but
preferably without spaces) you can continue with adding/importing/
checkouting :) /committing etc...

bye  Fabi