Hi Chris,

I've been using SCCS, which is very similar to RCS (see Applying RCS and SCCS from O'Reilly), with CGI.pm. I've ended up writing a simple wrapper for managing the SCCS archive from CGI. The main issues you will run into is permissions on the RCS/SCCS archive, concurrent access to the file(s) and security (running it under Taint mode for example).

My recommendation is to write a module with a simple wrapper with ONLY the functionality that you need and include it in your cgi script (use my_module). Perhaps something like:

• rcs_checkin()
• rcs_checkout_rw()
• rcs_checkout_ro()
• rcs_checkout_abort()
• rcs_checked_out_by_user()

Why put these in a module? It will be easier to test the functions in a regular script to verify that there aren't any errors or logic issues with the rcs subroutines. Debugging in a cgi environment is far slower than in a regular script environment IMHO

That should be enough to get you started in what you need.