Contrary to past experiences in my development control, version control can be easy and fun. Here's a list of tools I've used at work in the past:
- cvs :|
- perforce :\
- pvcs :(
- custom in-house vcs :(
- visual source safe :|
Of course, if you are a cvs expert and have been using it for years, I'm sure it's just as easy to keep using it--I don't hink svn is so amazing that everyone needs to go out and switch right now. But I was pretty pleased.
February 20th, 2005 at 04:53 AM Well, I've had a lot of issues with subversion so far. I know Jeff's sold on it, but I always end up with "DB corruption" errors at the most embarising times possible (when shoing svn to other Ph.Ds for example). It seems to work fine for a single user, but falls down flat with multiple people. The Mantis (mantis.cs.colorado.edu) repository is constantly giving errors, frustrating to say the least.
February 20th, 2005 at 01:32 PM is what we use at NI. and um. its not THAT bad, but it certainly leaves a lot to be desired. some of the simplest concepts are very chore like. that and its about slow as butt sometimes.
February 26th, 2005 at 04:48 PM The database corruption stuff is annoying, and its actually a problem with locking of the berkeleyDB database that subversion uses by default. Lots of other people hated it too though, so now they have the option --fs-type so you can specify what type of repository (I think "filestore"?) you want. svnadmin create --fs-type fsfs /home/yomama/repos All is good, yes!
February 26th, 2005 at 04:49 PM I don't like how it formatted my last comment. The svnadmin line should be on another line... Can I use html here?
svnadmin create --fs-type fsfs /home/yomama/repos