RE: RE: Visual Studio.Net and Subversion - Will this make it into a release?

Just adding my two cents to a discussion that really should continue on
the sourcecross.org dev list..

> API provider and the IDE, there is a good chance we will decide to use
a
> custom compile of Subversion

Which does not imply that we'll just change the #define as the
subversion faq exists. After all, doing a change like that will
introduce compatibility problems with every other Subversion
implementation out there! It's far more likely that we'll have to read
this from %appdata%\subversion\config or something, on a
per-working-copy or per-url basis. That's quite a lot more work than
just changing a #define and recompiling.

But, the Sourcecross provider will rely on tSVN/RapidSVN or SVN.EXE for
all operations that the SCC API does not support. We're not going to
build our own GUI. This implies at least some of the other products will
also need to behave the same way - and the best way to do that is to
patch the subversion client code (libsvn_wc).

And as people have said, it's only a problem with web projects and is
quite possibly going to be fixed in Whidbey - however far off that
really is :-(

I'm afraid your best bet for the short term is to scratch your own itch,
unless you can find someone else with the same itch. We
(sourcecross.org developers) are very aware of the issue, though.

- Walter

(PS Sorry Kevin for accidentally sending this to you. Since the
sourcecross mailing lists are reply-to-beneficial, I'd got out of the
habit of reply-to-all!)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 8 00:41:25 2004