| |
|
 |
Version Control management with CVS - Part 3
|
Managing modules
One thing you might have notice with the imported project was that when you checked it out you got a directory structure like music/apollo. From my perspective this is unnecessary since we need to go inside the music directory before getting to our project. To remedy this we can use CVS modules. They are basically named aliases for one of your CVS directories.
To add a new module we need to get access to one of the CVS administration files, namely the modules file. This is done by invoking
You should now have a directory called CVSROOT, look inside it and should find the file modules. Now edit it with your favorite editor, go to the bottom of it and add
Now commit your changes (update in case others have change it), remove the CVSROOT directory and try and checkout our newly named project and do
Voila, our project now resides directly in the apollo directory ready for development.
The modules file has other interesting features such as automatic include of sub-projects, but I'll leave that to another part.
Comment List
There are no comments.
|
|
|
|
