Re: Change management with cvs

["David Morris" <David.Morris@xxxxxxxxxxxxx>]

Rolf,

One way to learn about CVS is to try it out. There is an NT
version you can download and install from:

http://www.cvsnt.org/

Once you get it downloaded you would install it and set
up a repository. It has been a while since I set up a new
repository, but it is pretty easy. Since it seem like there
is some interest in this, I will see if I can go through the
exact steps and post them.

You will also want to set up CVS clients. Here is a page
that describes that process with WinCVS, which is a
nice gui client:

http://www.devguy.com/fp/cfgmgmt/tools/install.htm

With CVS you have a copy of your source in your CVS
repository. When a client checks out the repository, a
copy of the repository is made on the client machine.
The copy will include some management files in each
directory that are stored in a directory called CVS.

You can check out a copy of the CVS repository to
your PC without the management files. This is known
as an import. You don't change an import, you use
this to replicate the repositories contents.

Concurrent updates are done independently and
conflicts are resolved when you check changes back
into the repository. Checking something in is known
as committing. CVS does a pretty good job of merging
changes but you should always verify the results of a
merge yourself.

You cannot lock source but you can set yourself as
an "editor". CVS does not manage this for you, it just
provides a way for you to check for editors. You can use
this facility to identify concurrent updates before they
happen.

That is the 10,000 foot overview.

David Morris

>>> mailing-lists@r-m-e-d-v.de 04/19/02 10:58AM >>>
> I use it extensively to manage source. What are you interested
> in knowing?

I would be interested in some starting point. perhaps a book
like "the first steps towards CVS" or the like

TIA Rolf