COLLABNET SVN CLIENT INSTALL

There's also the question of how the code is compiled and tested.

In fact, if you look at TortoiseSVN's on line documentation on svnserve, you see they tell you to use CollabNet's version of svnserve. The TortoiseSVN project provides a complete set of command line tools, but really doesn't support them. The main difference will be one of support. TortoiseSVN and CollabNet uses the same set of source files to build their command line tools. The source for Subversion (which is from Apache) is free and open. (Alternatively, see about getting that 'no web servers' ban lifted and give Subversion Edge a spin for yourself.)

I suggest you get your users to qualify what, precisely, they want, since neither of the options they seem to be suggesting offers additional technical value which is overwhelmingly obvious but also fits within your deployment limitations. Unfortunately, it is Apache-based (and distinctly not svnserve-based), so I don't think it would pass your strict 'no web servers allowed' policy. As Subversion server packages go, it's a good one, but it's specifically because Subversion Edge provides a clean interface for such actions as 'Create a new repository' that I'm supposing your users mean Edge when they say merely 'CollabNet Subversion'. (At the risk of sounding like an advertisement) Subversion Edge offers a free, open-source, web-administered Subversion server in a single easy-to-install package.

COLLABNET SVN CLIENT INSTALL

I can't help but wonder, though, if the folks urging you to install 'CollabNet Subversion' are, in fact, urging you to consider CollabNet's Subversion Edge product. The primary difference will be the additional support offered by CollabNet for the version they provide. It's difficult to imagine what immediate technical benefit you'd get from running CollabNet's packaged 'svnserve' utility versus the one that ships with TortoiseSVN. FULL DISCLOSURE: I am a veteran Subversion developer and a CollabNet employee.

Collabnet svn client