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

Re: Feedback/experiences on PushOK SVN

From: Ted Dennison <dennison_at_ssd.fsi.com>
Date: 2006-07-14 17:47:51 CEST

Erik Hemdal wrote:
> PushOK SVN has been suggested to me as a way to use Subversion as an SCC
> provider for some of our IDE tools. But my source didn't have any
> specifics, only that it is supposed to work. Does anyone have experience
> with this SCC plug-in that they can share?
>
I looked at using it, but we decided against it because we wanted
sources for our integration tools. It looks really nice though. Why not
download it from their website and try it out for yourself?

The main problem any SCC provider has with Subversion is that the SCC
spec was designed around SourceSafe. Among other issues, this means that
everything is geared to a strict-locking style of development, which is
not really the Subversion Way.

If you are just interested in VisualStudio integration, another thing
you might be interested in trying is Ankhsvn. (
http://ankhsvn.tigris.org/ ). Sadly, we couldn't use that either, as its
.NET, and we are still using VS6.

I ended up having to write our own Subversion SCC provider, which I'm
still working on in the rare moments I have time to spare. Sadly, I
can't share it, as Micro$oft made us sign an NDA before they'd let me
look at their (inadequate) SCC docs. Its a lot of work, so I'd say
PushOK's software is definitely worth the money if it works OK for you.

-- 
T.E.D.   Work     -  mailto:dennison@ssd.fsi.com
         Home     -  mailto:dennison@telepath.com (Yahoo: Ted_Dennison)
         Homepage -  http://www.telepath.com/~dennison/Ted/TED.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 14 17:49:39 2006

This is an archived mail posted to the Subversion Users mailing list.

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