CVSspam Documentation


Table of Contents
1. Installation
1.1. Configure CVS
1.2. Installing CVSspam files
1.3. Configuration File
1.4. Debugging installation problems
2. Configuration Options
2.1. Integration with Bug Tracking Software
2.2. Integration with ViewCVS/CVSweb/Chora
2.3. Global Email Addresses

For the latest version, visit http://www.badgers-in-foil.co.uk/projects/cvsspam/.


1. Installation

1.1. Configure CVS

To install CVSspam you'll need to alter the repository's configuration files.

Check out your repository's CVSROOT.

Alter commitinfo to call the CVSspam script that records the directories that have been commited:

Now you need to alter loginfo to record the log entry made by the user (and send off the email):

Note

The expression you use to select the project (the first thing on the line) must be the same in commitinfo and loginfo.

Commit your changes to these files. You should see a message from CVS like 'rebuilding adminstrative database'. You are now be ready to test the setup.

Checkout a copy of myproject and commit a change. An email should be sent to the address you specified.


2. Configuration Options


2.2. Integration with ViewCVS/CVSweb/Chora

If you have ViewCVS, CVSweb or Chora web-access to your repository, CVSspam can generate links to it in the emails. Links the file before and after the commit are very useful for images, as only changes to binary text files are mailed. You'll get a link to the side-by-side view of the changes as well.

To enable ViewCVS support, specify the URL of the top-level ViewCVS directory in cvsspam.conf.

For CVSweb, specify the URL of cvsweb.cgi,

For Chora, specify the URL of the directory containing cvs.php,