The Science of Debugging
Chapter 3


3.2.5 Checking Out Modules From CVS


Now it's time to test and see if what you put in was what you wanted; cd to the directory previous to the one you put in. Rename your original directory, something like "backup" works fine - doesn't matter, it's just for backup reasons. Then, we want to checkout the code. I would type;

> cvs checkout cvstutorial




If you used the mud example, you'll want to replace 'cvstutorial' with 'src'. The last argument is the directory you saved to - or it could be the module name. For now, we'll just ignore module names though, and stick to directories. Lets verify that the checked in stuff is the same as the checked out directory - I'd type;

> diff -r cvstutorial backup




The code (text) files should be the same. Notice though, that CVS only stores text-mode files.. so there won't be any binary files like executables or object (.o) files. You can add these specifically with the -k option , or the -i option, but these are left as exercises to the reader.

You should probably now delete your old directory. If you leave it around, people may mistakenly make changes to IT instead of your actual version. If you're not ready for that leap of faith, just make a backup with tar, save it somewhere safe, and then erase the directory.



Index
3.2.4 Adding Modules to CVS 3.2.6 Commonly Used Commands