[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [TSVN] VisualStudio.NET and TortoiseSVN integration

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-07-08 19:52:43 CEST

"Erik Anderson" <erikba@teamworkgroup.com> wrote on 07/08/2005 12:29:16
PM:

> There are enough failed projects out there attempting to create an SCC
> Proxy that I would strongly hesitate before trying to dive into that
water
> again. Although I would really like to see an SCC proxy (FrontPage
> anyone?) the interface is probably too restrictive to allow an SVN-style
> lock-less versioning system.

I think there are two big reasons for this:

1) It is a lot of work. Reusing TortoiseSVN could drastically reduce the
effort, as well as improve the quality. You would be starting off with
the assumption that the end result is going to be good.

2) The SCC NDA. This is not compatible with the GPL and makes it hard to
build a community. My idea is for someone to write an SCC Proxy that
shields TortoiseSVN from the NDA. The proxy would just be a DLL and
whatever it took to register the SCC provider. It could then hide the
details of the NDA behind its own interface that could be made public.
Someone could then get the public side of this interface to work with
TortoiseSVN.

It is probably a pipe dream, but it sounds feasible and could make this
work.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Jul 8 19:53:03 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.