Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a module in my repository. Let’s call it module1.
If I just checkout it, it’s alright, it shows up in my machine and I can work on it.
There’s a parameter in checkout command named -c – according to help, ‘”cat” the module database.’.
But when I run this command
cvs co -c
The module isn’t showing up. Why? Is there a cache file, something in my machine that needs to be updated, flushes or something? module1 exists, but doesn’t show up when cvs co -c is called. Why?
cvs checkout -csimply dumps the contents of the $CVSROOT/modules file in alphabetical order minus the comments. This file has to be maintained manually. You can find information about it in the CVS manual.If you want to list physical modules (as opposed to the virtual modules defined in the
modulesfile, then what you’re looking for is thecvs lscommand. Note however that this command is only supported as of CVS 1.12.x as well as by most versions of CVSNT.An alternative approach for listing physical modules that also works with older versions of CVS/CVSNT is described in this answer:
How can I list files in CVS without an initial checkout?