Erik Forsberg wrote:
> Hi!
>
> I'm looking for recommendations for using Subversion for version
> control in a small software development company.
>
> We have a very heterogenous Linux environment which means that there
> are many different versions of subversion in the different
> distribution's package systems. Doing a quick check, I can find
> subversion 1.2.3, 1.3.2, 1.3.1 and 1.1.4.
>
> We're currently accessing our CVS repository via a shared NFS file
> system. I'm thinking that it's maybe best not to use the same method
> for subversion, given the wide variety of subversion versions on the
> workstations, and possibly other factors that I don't know about.
>
> Any recommendations?
Update everyone to 1.3.x. Seriously, features such at the "force unlock"
feature are well worth hving, and are available only in recent versions.
> http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html says
> in a warning that I can create an FSFS repository (which was my plan
> anyway), but seems to recommend that you use apache or
> svnserve.
Yeah, but that's on the server side. The client side should also be kept up
to date.
> Perhaps svn+ssh, using existing accounts, to a server keeping the
> repository on local disk is the way to go? Any ideas on the
> performance of that compared to direct NFS access?
I want to highly recommend HTTPS/WebDAV. It works quite well, and provides
easy read access for non Subversion clients.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 3 20:21:14 2006