Oh well. We lost.

[Tony Zakula]

On Wed, Jun 16, 2010 at 3:25 PM, David Dyer-Bennet <dd-b at dd-b.net> wrote:
>
> On Wed, June 16, 2010 13:43, Tony Zakula wrote:
>> On Wed, Jun 16, 2010 at 1:26 PM, David Dyer-Bennet <dd-b at dd-b.net> wrote:
>>> Looks like the development team at work has decided to go with a
>>> subversion setup for our new source control environment.  That won't be
>>> too bad an outcome, but I was working to sell them Mercurial, and
>>> apparently didn't do it well enough.
> [snip]
>> I use both as a consultant depending on what the client has.  I see
>> strengths in all the source systems.  I think the best solution really
>> depends on the project or environment.  However, one of the main
>> selling points for me on a new project was the cgi to serve multiple
>> repos without having to involve web dav.  SSH on Windows causes lots
>> of pain, and although I do not use Windows, other people do.
>
> Hmmm; I don't recall any difficulties setting up the Subversion server
> under apache (two years ago here), and it's certainly been trouble-free
> ever since.  Is the objection to web_dav something other than difficulties
> setting things up?
>
> It's certainly true that the Mercurial multi-repository server was trivial
> to set up, did that just the other week.  However, it takes more detailed
> administrative attention to add new repositories, including hand-editing a
> config file.
>
> I didn't consider using ssh-based repository access primarily because I
> wanted to use the corporate ldap server (well, Windows AD)  for
> authentication.  But I use Putty ssh from Windows a lot and don't notice
> any issues, including using it with rsync for gigabytes of file transfer
> on occasion.
>

>Is the objection to web_dav something other than difficulties
> setting things up?

I guess it is more of a personal preference for security, and a want
to keep things simplified from a system administration point of view.
I wouldn't say it is not trivial using Apache, but if you do not want
to use Apache, or need to use something else for other reasons, Web
Dav implementations can vary quite a bit.  Also, differing Web Dav
clients can cause headaches.  At least with the Merc CGI, it is all
pretty standard across every client and server.

Putty does work well.  I should have clarified.  I have seen many
developers struggle to use ssh/svn with Eclipse or Netbeans on
Windows.  Some have no problem at all.

I am always assuming use on a public facing server.  Obviously, for
corporate use inside a network, there are probably less security
issues and other considerations.

Thanks,

TonyZ