[kepler-dev] draft conversion of ptII tree from svn to cvs and svn nits

[Matthew Jones]

Hi Christopher,

We're using FSFS as the backend, which is the default on the binary 
packages of svn for linux.  I think using FSFS is much better than BDB, 
and you should go with the SVN default and use the file system if 
possible. That probably explains the size difference you are seeing in 
the repositories.

I'm perplexed why you say that FSFS isn't possible under solaris -- it 
works on the other OSes.  Is there some specific solaris bug?  It seems 
you've struggled with building svn for solaris.  My experience on linux 
was that it took about 15 minutes to install it and get it running 
initially under apache, including downloads.  Then I spent another day 
or so integrating it into our local systems like LDAP and changing the 
hook scripts, etc.  We've been testing for about 7 months now on other 
repositories, and have found it is a much nicer system to administer. 
So we're pretty much done with the setup, and simply need to move the 
kepler repository over using cvs2svn when we're ready to switch.

Matt

Christopher Brooks wrote:

> I'm running svn under Solaris, so I'm using Berkeley DB.  I'd prefer
> to use fsfs, but that appears to not be a possibility under Solaris.
> Using a database here adds complexity, fragility and makes backups
> harder.  A file system is a fine database for files, using Berkeley DB
> was a poor design choice.
> 
>    
> _Christopher
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Matthew B. Jones
Director of Informatics Research and Development
National Center for Ecological Analysis and Synthesis (NCEAS)
UC Santa Barbara
jones at nceas.ucsb.edu                       Ph: 1-907-523-1960
http://www.nceas.ucsb.edu/ecoinfo
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~