Since the goal of SVN is to be a compelling replacement for CVS, I
thought you might be interested in why we have decided not to switch
away from CVS. Please redirect this message to /dev/null if you do not
care. This is purely an informational email only.
We need the equivalent functionality of CVS Modules. We organize our
repo by functionality and then use CVS Modules to create projects that
pick-and-choose the appropriate library code. This allows us to share
our library code effectively.
We found that svn:externals was not sufficient for us because it
requires hard-coding the protocol. We could probably live with absolute
directories, but access to the repository is not consistent across all
our users. We also found that svn:externals causes a severe performance
penalty and commits do not recurse into them.
We considered implementing such a feature ourselves to give back to the
community, but after searching through the mailing archives we see that
this has been a feature request for *many* years and that several others
have already submitted patches that have not been incorporated. It
appears that this feature is not even on the radar of the svn developers.
We have been using CVS for a many years. We would love to switch to
something that overcomes its short-comings, but SVN is not the answer
for us. Thus, our evaluation of the SVN found it not be a "compelling
replacement for CVS."
Thanks,
Lane Brooks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 7 14:51:18 2006