On Fri, 6 Oct 2006, Andrew McNabb wrote:

- 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 is the default now (and has been for at least a year).  And yes,
BDB is terrible.

The BDB problems are supposedly fixed in Subversion 1.4.

I'm much more comfortable with FSFS too, though.

- 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.

Yeah.  Having to add a -prune to find is a little annoying, but it's
nice to be able to do some basic operations without being connected to
the network.

You get the best of both worlds with SVK. It has everything locally that you need, but stores it outside the tree so grep doesn't encounter any version control metadata. It also takes much less disk space than Subversion, but still doesn't need the network. And then it adds local version control separate from the repository. It's really very nice. I didn't quite get it till I watched someone else use it, but then it was obvious how helpful it is. It's excellent that it uses standard Subversion repositories as well.

Jon

--
Jon Jensen
End Point Corporation
http://www.endpoint.com/

--------------------
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