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

RE: Re: Determining TrotoiseSVN version from a script.

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

Good call on getvers.exe.

Unfortunately, not all components shipped with TortioseSVN contain version information.


-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn@gmail.com]
Sent: Friday, August 03, 2007 2:46 PM
To: users@tortoisesvn.tigris.org
Subject: Re: Determining TrotoiseSVN version from a script.

Kevin Grover wrote:

> There are probably even some programs around that can grab the version
> details from an EXE file (I believe it's a fairly standard MS format).
> You could use such a program (or write one) to get the TSVN proc exe
> version information.

No need to write your own:
scroll down a little bit. The file is called GetVers.exe.

> I understand the problem of TSVN and svn getting out of sync ---
> either can silently upgrade working copies that will then no longer
> work with the other client.
> However, your case seems to be an issue of wanting to use a program to
> fix problems of people not following procedures. If you tell your
> people to NOT install new versions, and they do, yell at them. If
> they keep doing it, fire them.

Don't fire them! Let them clean up the mess instead.

> Alternatively, lock down the computers so that users can not do those
> things. NOTE: even if you lock down the computer, a user could still
> unpack an svn-win32*.zip distribution into his path.
> Locking down the computers rarely solves as many problems as it creates.

Right. Locking down development computers makes developers leave and get better jobs.

> Threating to not use TSVN if the problems aren't fixed to your
> satisfaction, is probably not very helpful.

I usually do the opposite of what people ask of me when they threaten me. So be careful :)

> That said, some of the items you mentioned (having the /version
> qualifier) could provide some benefits (e.g. sanity checking in
> scripts) and not interfere with other TSVN functions.

That's not really needed. Also: TSVN is a GUI client, not a Console app.
Which means it doesn't even have an stdout.

> Another possibility for the TSVN team: since it is so common to want
> both TSVN and the SVN command line clients, perhaps TSVN could, as an
> option, be bundled with the svn command line clients (and SVN Book)
> and thus share all the libraries, config files, etc... from one
> install? I'm not sure how much work that would be to add, but it has
> the potential of preempting many of these problems. It may just be
> more of a headache than anything else. The only real difficulty I've
> seen in keeping TSVN and SVN in sync is that TSVN releases new builds
> faster than the SVN group get their Windows install files up. You can
> still use the zip files though.

That will never happen. The TSVN installer is almost 9MB in size as it is. Adding more to that will make people angry. And also people will think that since we ship those, we have to support those too.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
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:01:23 2007

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

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