Re: [OT?] SCM recommendation for small to medium size Perl projects

In your circumstances I would go with SVN for two reasons:

what you learn at home, you can use at work
client availability

One thing to note however, is that if you start with cvs, there is a script which allows you to convert to svn. To the best of my knowledge, there is not an automated way of going from svn to cvs.

From the command line, I have found cvs to be limiting, but fairly straight forward to use whereas svn can be a royal pain.

Both have supporting modules in at least perl and java and integrate via plugins with Eclipse and a couple of other IDE's.

I keep track of my stuff in cvs because it is all that I need, and my situation is similar to yours. Good luck in your decision :-)

...the majority is always wrong, and always the last to know about it...

Comment on Re: [OT?] SCM recommendation for small to medium size Perl projects

Replies are listed 'Best First'.
Re^2: [OT?] SCM recommendation for small to medium size Perl projects by Joost (Canon) on Mar 06, 2007 at 00:17 UTC
From the command line, I have found cvs to be limiting, but fairly straight forward to use whereas svn can be a royal pain. Really? In what way? I found svn to work mostly the same as cvs from the command line, except that it also does renames and works with directory trees (instead of just same-name files, as cvs does). I've always prefered the command line interface for both instead of the GUIs, anyway. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^2: [OT?] SCM recommendation for small to medium size Perl projects by blazar (Canon) on Mar 06, 2007 at 20:59 UTC
what you learn at home, you can use at work Very good point. Although at the moment I am so "lucky" as not to have to work... client availability This is another very good point. Although it also contributes to confuse me. The point is, up to some time basically there was only CVS, at least speaking of free SCMs. Now there's a flourishing of just so many of them that it's hard to pick up one. Well, not really: it's easy, but one wonders what each and any of them would have to offer him. Having multiple clients to choose amongst is somewhat yet another situation of the same kind. One thing to note however, is that if you start with cvs, there is a script which allows you to convert to svn. To the best of my knowledge, there is not an automated way of going from svn to cvs. Oh no, as I explained in my answer to GrandFather's reply, I don't see any advantage in starting with CVS and most probably I won't do so... From the command line, I have found cvs to be limiting, but fairly straight forward to use whereas svn can be a royal pain. In which sense? Although I kept forgetting things frequently enough to continuously have to ask coworkers for tips, I remember from my experience with SVN that most operations mimicked common NIX filesystem managing commands and utilities, thus it was rather easy to use in this sense. Both have supporting modules in at least perl and java and integrate via plugins with Eclipse and a couple of other IDE's.* Well, interesting to know. But I don't use any IDE anyway. Just a plain old text editor. (However last I checked there was a CVS mode for it, and I bet a SVN one is available too; it's own sources are maintained under Subversion.)	[reply]