Looking Past CVS: The Future is Distributed
Posted Dec 2, 2004 13:07 UTC (Thu) by aleXXX
Parent article: Looking Past CVS: The Future is Distributed
Well, why should the future of SCM's be distributed ?
I know more or less nothing about distributed SCM's, but I think it is a
good idea to have one central server where the current official version
of the sources lives. If you need the current version, get it from this
server. Which advantages do distributed systems offer ?
One thing about cvs: it has some problems, these problems are know. It's
damn easy to set up, run it's daemon, and all files exist as plain text
files on the server. If something goes wrong, you can just go and delete/
move/rename/whatever the files on the server directly.
That's currently my main "fear" of svn: I read about the installation,
and found something about apache, LDAP (or was it WebDAV ?, I'm no expert
in these topics) and that the sources are kept in a database.
So if I would switch to svn, I would switch to a SCM which does a lot of
things I don't understand and where I can't "debug" stuff. So I'll stay
with cvs for the near future.
to post comments)