Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Journal of IlyaM (2933)

Friday October 03, 2003
05:31 AM

Opensource version control systems review

[ #15036 ]
Just found quite interesting review of different opensource version control systems.

As for me I'm trying to choose between Aegis and arch. I'm looking with very big suspect on subversion - my guts feeling is that subversion is too overengineered. Instead of solving real VC problems we see Apache intergration, WebDAV, binary db backend. At the end from the point of view of end user (i.e. me) it doesn't offer much more then old CVS.

P.S. And, yeah, BitKeeper rocks. But it is too expensive for us.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Commercial Options (Score:3, Informative)

    by Matts (1087) on 2003.10.03 7:39 (#24647) Journal
    We've been evaluating commercial options here for a short while. Our requirement for this is to work on both Unix and Windows, so all the open source options are out. Candidates have been Perforce, Bitkeeper, MKS, AccuRev, PVCS and probably others.

    The most interesting looking tool appears to be AccuRev. It appears to be very simple to use, yet have a powerful branching model. I'll try and report more fully on it when we start doing a proper eval.
    • Our requirement for this is to work on both Unix and Windows, so all the open source options are out.

      Why not CVS itself? Obviously it runs on Unix, and I've found the CVSNT port ( to be quite nice. Plus, there's a plethora of Windows-, Unix-, Java-, and web-based clients.

    • How can you rule out open source on that account?

      The CVS client [] for Windows tortoiseCVS [] is actually quite ok - I expect you a familiar with the Unix client.

      I understand if you have special requirements, but you do not list them here, so it is hard to say.
      • You're right, I didn't list them as I've listed them before in my journal. Basically we need fixed branching and merging along with ease of use for the Windows guys. And it needs to easily support very large projects (which is somewhere that SVN currently falls down I believe).