> > The first and biggest obstacle is that the members of my team don't
> have
> > expertise in setting up a web server. Network administration and
> network
> > coding are far from our area of expertise. CVS does not require you
> to be
> > an expert in anything to install and use it. Subversion obviously
> > requires
> > more work and greater expertise to get your repository up and running.
> Do
> > you not consider this to be a significant drawback?
> >
>
> That's so not true. CVS does require you to be an expert in lots of
> things to install it and use it well. Including making sure regular
> backups happen, and all of the odd/fun situations that remote CVS
> repositories get into. (wedged locks, etc...)
>
I disagree. I use CVS at work to support me and about 8 other developers
of the software I work on. I've done all of the setup work. The machines
already had to have ssh setup to allow secure remote access (we don't use
any firewalls). Compared to creating a local CVS repository, the only extra
work was adding a few additional user accounts to the machine hosting the
repository. I've never had any problems with wedged locks or anything else
on the server that required my interaction to resolve. Total setup was
a few commands to create the repository, creation of some user accounts,
installation of SSH key-pairs for these users, and addition of a couple
environment variables for CVS. In comparison, I spent 4 hours once trying
to set up a SVN repository for the code over encrypted connections. That
was before I gave up. I'm certainly no expert on web servers which probably
added to the setup time for SVN, but I've never had to be to do version
control before. As for backups, with CVS I can do a backup using scp which
is really easy to do and easily automated with a cron job. With SVN, I would
have to look up the backup procedures for BDB and find out the proper way
to backup since I don't know if simply copying the files would work.
- Scott Lenser
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 30 22:34:59 2002