On 10/6/06, Gary Thornock <[EMAIL PROTECTED]> wrote:
--- Nathan <[EMAIL PROTECTED]> wrote:
> I second the suggestion to go with Subversion, and not CVS.
> We used CVS at my work until we tried Subversion a few years
> ago-we switched and never looked back.  Subversion is waaaay
> better.

Both have their good and bad points.  I prefer CVS for most
projects, although to Subversion's credit, it does offer atomic
commits and better support for Unicode files.

And subversion doesn't mess up binary files (yay, no messed up
images!), and even uses binary diffs for deltas.

Why do I prefer CVS, then?
- Independent revision numbers per file, rather than a single
  number for the entire project

That's definitely a difference--funny, though, that that's one of the
things I _don't_ like. :-)  And it's not just one number for the
entire project, it's one number for the entire _repository_.

- Better branching and tagging

I'll have to take your word for that.  I've never used branching and
tagging with CVS.

- I've seen too many cases where Subversion's Berkeley DB
  repositories have been corrupted or left in a locked state,
  preventing everyone from updating or committing until an
  administrator can fix things.  In partial response to this
  problem, Subversion has added the ability to make a
  repository using the native filesystem instead of BDB, but
  BDB is still the default.

FSFS has been an option since 2004, and has been _default_ since 2005.
I agree that BDB sucks (the first subversion repository I ever made
was with 1.0 using BDB and it got corrupted, but I was able to recover
it), but I've been using FSFS for two years without a single problem.

I've had corruption problems with both CVS and subversion when using
BDB.  Always make backups!

- Subversion keeps a second copy of every file in the project
  in hidden subdirectories within the working copy.  Besides
  being a ridiculous waste of disk space (keep in mind, I use
  a laptop, so disk is at something of a premium), this also
  causes problems when doing multi-file operations like
  "find . -type f ..." or "foreach i (`grep -rl foo .`) ..." .
  The rationale for this design was that disk is cheap and you're
  not always connected to the network.  I disagree.  On a laptop,
  disk is expensive, and between WiFi and EVDO, you pretty much
  *are* always connected to the network if you want to be.

I also use a laptop.  It "only" has an 80GB disk.  What in the world
do you keep in CVS that's so huge that doubling it wouldn't fit on
your disk?  Subversion is not a file storage system, it's a version
control system.  The benefits of keeping the "ridiculous" copy of
everything include 1) the lightning fast ability to show all local
changes you've made along with diffs (if you like) without touching a
network connection, and 2) the ability to revert local changes without
touching the network, etc.

For "multi-file" operations, try adding "| grep -v .svn" to filter out
.svn directories from the results.

As for the "always connected" thing, that's not very true for a lot of
us who travel, especially when you're flying.  And I've never met
anyone with EVDO (I assume that's a satellite internet connection or
something similar).  Certainly no one that uses my repository has it.
Also, many of us have repositories that aren't publicly available
(like my work) -- which makes CVS all but useless anywhere but in the
office, while I can do quite a bit with subversion since one if it's
goals is to not touch the network unless it has to.

Anyway, don't feel like I'm attacking you or anything, because that
isn't my intention.  I've just had a lot of experience with subversion
and have yet to encounter any of the nightmares I had to deal with in
CVS.  (like "why the heck is the nice PDF I committed all scrambled
when I check it out?")

~ Nathan

--------------------
BYU Unix Users Group http://uug.byu.edu/
The opinions expressed in this message are the responsibility of their
author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to