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

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.
  • 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 ( [])

      • 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 subversions branch/tag model []. You get cheap branches and you avoid branch-point tagging since there is no branch/tag distinction, everything lives in the same space. Seems a much simpler model to me but YMMV.

        On the distributed development one advantage is that you only get the diffs in any change sent over the wire which can make working with the repository much faster.

        Being able to associate arbritary meta-data with files and directories is interesting too. For example I'm playing with marking failing tests with meta-data and then preventing commits until the tests pass :-)

        Obviously if CVS works for you go for it, but I really would give it a try.