![]() |
Chapter 3 | ![]() |
/home/cvstutorial/work
/home/cvstutorial/work/fileone
/home/cvstutorial/work/filetwo
/home/cvstutorial/work/directoryone
/home/cvstutorial/work/directoryone/filethree
To place these in the CVS repository, I have to use the CVS import command. I'd type
> cvs import -m "Original Source Code" cvstutorial dughi start |
.. from the cvstutorial directory (it's very important since the location of the repositories you create are based on
where you added them from)
Let's break down that command.
-m "Original Source Code"
This is a way of adding a note to this revision for the history file. If you look at the history of each version, you'll see this guy in the description field. If you like, you can leave this out, and you'll be kicked into an editor (vi by default, use CVSEDITOR env. variable to override) and have to supply a message anyway.
cvstutorial
cvstutorial is the directory to which the code will be stored in, in your CVS root directory. Remember this name - when you checkout code from the repository, you'll use the directory you want as the argument.
dughi start
The other two arguments are the vendor tag, and the revision number. These are usually not important - they're used for external modifications, like outside teams providing you with a patch that lets your program run on a different OS (for example). The vendor tag specifies the vendor/team name, and the release tag is a string to identify the release (usually a version number, but they're not used in our example, so it doesn't matter).
If you're going to use this to store a mud, for example, you would cd to the /src directory, and type in something like;
> cvs import -m "Original Source Code" src the_coders 1.0 |
![]() |
Index | ![]() |
3.2.3 Initalizing CVS | 3.2.5 Checking Out Modules From CVS |