Go to the previous, next section.

Some questions about CVS and some (often weak) answers.

When I say cvs checkout module/sub-directory and then cvs release module/sub-directory it says unknown module name. why?

• because module/sub-directory is not a module in the modules file.
• cvs release module should work with this.

Because of incorrect releasing of directories, I noticed that cvs history reports that modules are still checked out. how do I correct this?

• by editing $CVSROOT/CVSROOT/history VERY carefully
• I do not know the correct way of doing this but the O lines are for checking Out modules. Removing the last O line that corresponds to the module in question may work.

If I just made a typo and started to check out a tree I did not want to. Can I hit control-c? What are the ramifications?

• probably some files are checked out while others are not
• it is not a good idea to do this. Unless you are pushing the limit on your disk space or something, just wait till it is done and then release the directory.
• don't know exactly

I screw up and removed the tree that I was about to start working on. How do I tell CVS that I want to release it if I don't have it anymore?

• maybe you can't
• you need to edit $CVSROOT/CVSROOT/history very carefully to fix this problem (see above)

What is the proper way to configure CVS for multi-user operations? What sort of file directory modes are appropriate aside from 770 modes everywhere. Any setgid support?

• first, CVS should NOT be installed as setuid or setgid!!! It is not designed to support these functions and will thus be a security problem. (the same applied to RCS)
• set all your $CVSROOT repository directories to a common group (src would make sense). Setgid on the directories would also be good if your system supports 'chmod g+s dir'
• normal 770 or ug+rwx directory modes in your repository directories should work. Have your system administrator execute something to the affect of:

  	find $CVSROOT -type d -exec chgrp src {} \;
  	find $CVSROOT -type d -exec chmod 770 {} \;
  
  	and (if available)
  
  	find $CVSROOT -type d -exec chmod g+s {} \;
  

• your default umask should be set to 027
• make sure all your developers are in the src group.

I am constantly running into different library modules to fix problems or add need features. This may not be a good practice but how does CVS fit in this scenario. Should I checkout the modules I need and once and a while commit them?

• yes. as long as you realize the commit will make your changes seen by everyone. make sure to run the appropriate tests on them, etc.

I have 4 releases of my debug malloc subsystem. They are 1.01, 1.02, 1.03, 1.05. Should I:

cvs import -b 1.1.1 -m 'Malloc 1.01' MALLOC_1_01 malloc_1_01
cvs import -b 1.1.2 -m 'Malloc 1.02' MALLOC_1_02 malloc_1_02
cvs import -b 1.1.3 -m 'Malloc 1.03' MALLOC_1_03 malloc_1_03
cvs import -b 1.1.5 -m 'Malloc 1.05' MALLOC_1_05 malloc_1_05

• not really. cvs import may not be the right may to do this. you should cvs import the first set of files then for each release you should:
  • copy in the new version
  • cvs add/remove the files that have been added/deleted
  • cvs commit the new version
  • cvs tag the files with the appropriate release-tag
  • repeat

When I use the above multiple-import method and I say cvs checkout malloc I do not just get the files that correspond to version 1.05 . I get all of the files. I have to say cvs checkout -r malloc_1_05 malloc to do this. Is this correct or do I need to cvs remove the files that have been removed between the different versions?

• yes, you need to cvs add/remove files to have the repository know about them. the files that are removed are placed in the attic so that old-revisions can find them.

Is there a CVS feature to tell me what files have changed, what are new what have been removed from the current directory?

• when you do a cvs update, CVS will inform you of the changed/modified files with a M, updated files with a U, and removed files with an R. It will show you files that might need to be added with a ?.
• in the contrib directory under the CVS release there exists a cvscheck script which gives you some of this functionality.

If I had a file at one point, but I did a cvs remove on it, and now I need to recreate it. How can I re-add it? It complains that it is in the Attic. Can it live there for old versions but also exist the in normal repository for newer versions?

• No it cannot live in both the Attic and the repository.
• I believe you can move the file out of the Attic directory by hand. this seems to work fine.
• WARNING: playing with the repository files is a potentially dangerous situation. You may wish to let your system administrator take care of this. If you are doing it yourself, make sure to use cp -i and mv -i or just watch your back and take your time.

Go to the previous, next section.