[Babase] Revision control -- switching babase from cvs to arch
Karl O. Pinc
babase@www.eco.princeton.edu
Fri, 15 Oct 2004 13:38:03 -0500
One of these days before we go live I'm going to switch
program source code revision systems. Cvs is ancient
and something of a pain, although standard. The
drop-in replacement for cvs is subversion, but it
is somewhat heavy-handed in terms of what sort of software
must be present on the system for it to run. It would
require that Hunter be involved, webservers are necessary,
etc. Overall, I don't think that subversion's command-line
compatability with cvs is worth it. GNU arch is up-and-coming
and uses a completely different change management model
from cvs, which avoids the design flaws of cvs, and
is easy for me to install sans Hunter. Arch is building a substantial
user base and is not going away. It runs on all sorts
of Unix, including Mac OS X, and there are apparently versions
that run on MS Windows but I don't believe the Windows version
is full featured at this time.
I chose CVS initially because Tyler wanted to go that way
and because ARCH may not have yet reached 1.0 back then.
Now it's at 1.2. Looks like there's a program (cscvs)
that will import cvs history into arch, so if it's easy
I'll do that. Otherwise I'll just keep the old cvs
stuff around and start the arch change history whenever
I get around to switching over. Switching is just a matter
of starting to use arch instead of cvs.
http://www.gnu.org/software/gnu-arch/
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein