News
	Latest
	Archive
	Community news

Articles
	C++
	Communities and Content
	Databases
	Editorials
	Emacs
	General
	HTML
	Java
	Notices
	PHP
	XML

Links
	Apache
	C++
	Database
	General
	HTML
	Java
	Javascript
	Linux
	Object oriented programming
	Open source
	Perl
	PHP
	Python
	Ruby
	SOAP
	XML
	Suggest a link

About
	Advertise on zez
	Contribute
	Contact us
	About zez

Version Control management with CVS - Part 1

Author: Jan Borsodi

Publishing date: 01.11.2000 11:15

Checking out

If you already have a project that you wish to "check out" there a couple of simple steps to it:
What you first need to figure out is where the repository is located, if it's in the same place as the CVSROOT you set earlier you're set to go, if not you must supply a parameter to the CVS command.

The next thing you need to decide is which project you want to check out, this is either done with a path in the repository or with a CVS module name.

Checking out is done with the CVS command checkout

cvs checkout module

or the short version

cvs co module

where the module is either the name of the defined module on the CVS server or the relative path to the project.
To use another repository than the default you must specify this with the -d option, this is called a global option and is always put before the CVS command. So if we wanted to check out the RegExplorer project we would do

cvs -z3 -d:pserver:anonymous@cvs.RegExplorer.sourceforge.net:/cvsroot/RegExplorer co regexplorer

You should now get a local copy of the CVS project. You might have noticed the use of the global -z3 option. This simply tells the CVS program to use the gzip compression when sending data over the network, this helps the transfer speed when using the Internet, the number 3 is the compression-level for the gzip program.

The local copy will present in the subdirectory regexplorer on your local machine, the module name is always used for creating a local subdirectory. You can now enter this directory, look around and make changes.

Any changes you make to this project will not have any impact on the repository version, there are two reasons for this.
The first reason is that you accessed the CVS server with an anonymous user which only gives you read-only access. To get write access you will need a user on the repository server and checkout the project with that user.
The second reason is that any changes by you on your local machine will not be incorporated to the remote server before you do a commit. How to do a commit is explained in a future part.

<< Previous page | 1 | 2 | < 3 > | 4 | 5 | Next page >> | Printer-friendly page |

Comment List

There are no comments.