RCS via network?

From: Steve Kirkendall (skirkendall_at_dsl-only.net)
Date: 08/26/03 

Date: Tue, 26 Aug 2003 14:21:20 -0700

Is there a version of RCS that can use TCP/IP to read & write the "*,v"
files? Via FTP maybe, or a custom protocol.

Or if not that, then is there any way to make RCS store its "*,v" files
in a parallel directory tree? E.g., for the source file ~/src/foo/bar.c,
RCS would normally store the history in ~/src/foo/RCS/bar.c,v but I'd
like to store it in something like ~/RCS/src/foo/bar.c,v. That way I
could at least put the ~/RCS directory in an NFS mount and share the
history files that way.

Here's my situation: A couple of friends and I have been working on an
application program for the last 12 years. We now live in three different
cities, and support two different platforms. So we have multiple copies
of the RCS files and periodically we need to resynchronize our files.
I'd like to avoid that by storing the RCS files on a single system.

I'd like to avoid CVS because...

 1) It seems like overkill for three people.

 2) We have some shell scripts and Makefiles that use RCS commands.
    I'd rather not change those if I don't have to.

 3) I like RCS's strict locking. It is extremely rare for two of us
    to work on the same source file at the same time, and if we do it
    is probably because we're working on the same bug. It's worth a
    phone call to find out.