| 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 3 |
CVS is a Version Control System which helps multiple developers manage software projects. In this third part I'll show the details of CVS repository management, that is creating a new CVS repository, importing sources and handling CVS modules. Part 1, Part 2.
Creating a repository
Before you start creating a repository you need to figure out where you want to have it. Make sure you are located on the machine with the repository and entercvs -d /home/cvsroot init |
Exchange /home/cvsroot with the path to your repository.
You should then find a default setup for your CVS repository in your selected directory. If you look inside you'll find a directory called CVSROOT, this directory contains all your administrative files.
If you want to perform back routines on your CVS then simply backup all files found inside your selected directory. I suggest you read the postscript or PDF manual of CVS to get more information on CVS backup, there are a couple of issues which you need to know about.
If you're unhappy with the placement of your repository you can simple move the directory anywhere you want as there are no absolute paths in the configuration files.
Comment List
There are no comments.
