4.2. Testing manual CVS updates on Interchange catalogs
Next, lets again update the checkout we made a while back before importing our catalog. (Alternatively, one could use a visual CVS client detailed above).
cd ~/src cvs -q up -d foundation # -q for quiet, -d for directory prune/update
Additionally, you might test making a change to one of your checked-out source files, saving it, then committing it.
index.html: <!--this is a test comment at the top of index.html-->
Now commit the change
cvs commit index.html
Your changed version will now be resident in the repository. Again, CVS documentation is in the Resources Appendix.
This time, we can allow the changes to take effect on the code being used by Interchange to serve pages. To do so, one must run a cvs update on the catalog directory:
cd /var/lib/interchange/foundation cvs -q up -d #up is the shortened version of "update"
That should notify you of the new version it downloaded with something like:
You may also get something like the following:
M catalog.cfg M etc/status.foundation M ... ? orders/000001 ? ...
The ? lines in the above example mean that the CVS server has never heard of the listed directories or files (they are in your local source dir but not in the CVS source dir). It is harmless, but sometimes annoying, and can be taken care of with CVSIGNORE.
The M means that the file has been modified on your local copy, and is out of sync with the remote CVS version (e.g. when Interchange runs it updates etc/status.foundation). Normally this is corrected by uploading your "modified" version to the server, but in this case, the modification was done by Interchange instead of the programmer, and wasn't meant to be committed back to the CVS repository. See CVSIGNORE.
Now, check to make sure that your change has taken effect by refreshing the homepage on the site. To see the comment, use View->Page Source or whatever the relevant command for your browser is.
At this point, its obvious that it would be time consuming to manually run 'cvs up' every time you make a change to the source code, so the next step is to setup CVS to automatically update the catalog whenever you commit something to CVS.