Looking Past CVS: The Future is Distributed
Posted Dec 9, 2004 22:23 UTC (Thu) by anton
In reply to: Looking Past CVS: The Future is Distributed
Parent article: Looking Past CVS: The Future is Distributed
I really have trouble with your notion that CVS is easy to set
up. I've found it near-impossible to securely configure an anonymous
CVS which allows a few maintainers to update the repository.
If you find that hard, don't do it. Give accounts to your
maintainers, and let them use it with ssh.
In a large company SVN leveraging off Apache is a good
thing. Sysadmins already have authentication and authorisation
configured for Apache and extending this to SVN is trivial. So you get
to use your "real" userid and password. And it runs over HTTPS no
there's no fiddling about with SSH tunnels and craziness.
It runs over what? Our sysadmin wouldn't know how to make
Apache authentication use our "real" userid, and I don't know it,
We have sshd running on every server, and Apache on exactly one,
and that's a pretty crufty machine, where Subversion is guaranteed not
to install (it's even too picky for my Fedore Core 1 AMD64 box, and my
bug report about that to email@example.com vanished in the
In contrast, using CVS over ssh is easy and trouble-free, and I
don't even have to use a password (thanks to .ssh/authorized_keys).
No tunneling necessary, just set
and use a command like the following for checkout
cvs -d :ext:user@host:root-path checkout directory
Any chance that svn will ever be as convenient and simple?
to post comments)