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

RE: Re: Re: Determining TrotoiseSVN version from a script.

From: Bob Cunningham <bcunningham_at_sandel.com>
Date: 2007-08-06 18:08:30 CEST

What? Are you suggesting that such a simple feature would complex to
implement? I do not make such suggestions lightly, and I've tried to
keep the scope of my request as constrained as possible. I've even
suggested three different methods (one in the app, two in the
installer).

I am, of course, assuming some level of technical competency here. The
wonderful implementation of TortioseSVN is a strong clue that such
expertise does exist.

-BobC

-----Original Message-----
From: Andy Levy [mailto:andy.levy@gmail.com]
Sent: Monday, August 06, 2007 8:59 AM
To: users@tortoisesvn.tigris.org
Subject: Re: Re: Determining TrotoiseSVN version from a script.

On 8/6/07, Bob Cunningham <bcunningham@sandel.com> wrote:
> The Cygwin svn CLI client works fine, and has been totally error-free
> for me. We use Cygwin because it provides a single-point of update
> for a broad array of pre-packaged utilities. While Windows-native
> instances exist for some of these tools, most of which are faster than

> the corresponding Cygwin build, only Cygwin provides us with a single
> integrated update mechanism. Only Cygwin builds from the original GNU

> sources, ensuring developer builds done under Windows are compatible
> with builds done on our mix of Windows and Linux production servers.
>
> TortoiseSVN provides a rather different notion of compatibility.
>
> The fact that TortoiseSVN does not include the matching CLI app
> baffles me. It would be a trivial addition to the project. Even if
> the actual CLI binary weren't included, the TortoiseSVN installer
> could simply offer to TRY to get and install the corresponding CLI as
> part of the installation/upgrade process. At the very least, the
> installer should attempt to run the local CLI svn instance and try to
> detect the incompatibility before a user crashes into the problem.

<rant snipped>

Even if TSVN did provide the official CLI binary, it would result in the
same errors you're getting now. You would gain NOTHING.

The Cygwin client thinks it's running under a *NIX environment, and it
is well-documented that sharing working copies between OSes and
filesystems can result in bad behavior from the tools. Head over to the
Subversion Users list, and ask people if it's a good idea to run the
native Win32 binary and Cygwin binary against the same WC, and they'll
tell you the exact same thing.

TSVN is a GUI application. It's more than an application, actually -
it's a GUI shell extension. It seems pretty logical that it *not*
include a CLI, from my perspective.

Let the maintainers of the TSVN project decide what's "trivial" to add.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Aug 6 18:06:40 2007

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