On Oct 4, 2006, at 20:13, Steve Martin wrote:
> The last contract I was on, we needed an SCM system. I chose CVS,
> but the developers decided they wanted to try Subversion.
>
> So.. we went with subversion. We went with it, *I* dealt with the
> head aches, the fact that you can't make a simple commit without
> changing the version # of the entire repo,
> and so many of the other complaints / issues I've seen on this list.
>
> My new job also required an SCM system, and I set CVS up in half
> the time, without having to explain why the rev # of the entire
> repo and every file checked out changes during a commit, no
> "malformed this or that" errors,
> no issues with apache authentication, no issues with svn -d, nothing.
>
> It worked perfectly like CVS always has, which subversion never has
> for me or a lot of the others on this list.
>
> So... all I'm asking is, what is so great about subversion that
> would make people want to give up the tried and tested SCM system,
> for something that seemingly has so many problems?
>
> And the previous SVN setup was on RHEL 4, and the current CVS setup
> is on RHEL 4. I'm certainly not a noob to this kind of thing, and
> did RTFM before setting subversion up, but it never worked for us
> like advertised, while CVS worked exactly like CVS always does...
> import a file, only IT'S rev changes, not everything in that dir or
> the entire repo...
Why Subversion? Because the problems you mention should not occur,
and/or are not problems. I have never used CVS. I set up a Subversion
repository 18 months ago for our company of 10 developers. No
problems. No "malformed this or that" errors; probably something
misconfigured in your setup. I don't know what you mean with "svn -d"
problems. I don't know what Apache authentication problems you're
talking about either. We serve our repository through Apache 2 and
authenticate through Apache to our LDAP server. Works great.
As to the revision number of the repository, it sounds like you're
attaching a meaning to that number which in Subversion is not
present. In CVS, each file has a revision number. In Subversion, the
repository has a revision number. The number is exactly the number of
commits that have occurred in the repository. Nothing more.
This and other topics are addressed in the section of the Subversion
book for CVS converts. As I haven't used CVS I can't evaluate its
effectiveness, but maybe it will help in one way or another.
http://svnbook.red-bean.com/en/1.2/svn.forcvs.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 5 03:46:18 2006