Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Another version controls systems comparison 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Based on this comparison and other information I've seen, doesn't it just make sense to choose CVS for most OS projects?

    I recognize that some of the problems are painful for complex or heavily used development environments, but the ubiquity, the tools, the documentation makes it an obvious big win for most projects, doesn't it?

    Where I work, I'm going to be forced to start using CA's Harvest, which looks pretty involved, especially for small projects. Anybody have any comments or experience on this produc

    • Based on this comparison and other information I've seen, doesn't it just make sense to choose CVS for most OS projects?

      I've given an intro-to-CVS talk for a few user groups over the years. I'm constantly amazed at how many developers are working with significant bodies of code without version control.

      Then again, using version control wasn't the norm 10-15 years ago. And a lot of Perl programmers aren't professional developers, so CVS is just another entry on the "list of things I gotta learn" for

  • I have to admit I've thrown out CVS in favour of subversion. So much nicer to have version control over directories and renamings, atomic commits, only diffs over the wire, etc.

    Still technically alpha software, but it's been rock solid for me and I've now started using it with clients.

    (and, although I don't use it this way myself, there is something very cool about mounting a DAV subversion repository on your desktop and having a versioned file system :-)

    If you've not tried it play with it for a week. '
    • Maybe I'm just looking for perfection. I defentely was spoiled by trying bitkeeper. To me subversion looks like just a small improvment over CVS. File renames and similar things are cool but I definetely can live without them - I will not switch to subversion just because of them. What I really need, what really whould save my and co-workers time is robust support for distributed development and robust handling of branching and merging. Subversion is nowhere close to that.
      --

      Ilya Martynov (http://martynov.org/ [martynov.org])

      • I felt the same way, until somebody persuaded me to try it for a week. I now can't imagine going back to CVS unless forced. I really would give it a whirl - especially since you can now use the standalone svnserve server rather than having to muck around getting an Apache2 DAV server up and running.

        I have to admit I try and avoid branch/merge at all costs since I find the reintegration pain worse than the avoiding-branching pain - but I understand that isn't always possible. Personally I prefer subversion

  • * Yes, it has an annotation system. aeannotate
    * Yes, it has a way to diff the working version. aediff.
    * The documentation is available as plain text.
    * Yes, Aegis has a web interface.
    * Yes, there is a GUI for Aegis. tkaegis.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.