Including CLI client in TortoiseSVN installer?

[Magnus ...]

I'm sorry if this has been mentioned before and decided against on
architectural grounds. But it seems to me that it might make life
easier for a lot of people if the TortoiseSVN installer could
(optionally) install the CLI tools svn/svnadmin/etc along with the
TortoiseSVN binaries and (optionally) set the path to include the
TortoiseSVN directory.

In my case, TortoiseSVN is my main client with 95% of repository
access occurring through TSVN. However, a few times I need to use a
CLI feature, so I need to ensure that every time I update, I update my
CLI install at the same time (I'm using SlikSVN, without Apache
bindings, for that). Add to that the fact that TSVN helpfully includes
plink to allow svn+ssh connections right out of the box and the
benefits become even more obvious and pronounced.

The extra hassle of making sure I match both programs on upgrade
actually means that I upgrade much more seldom than I otherwise would
and end up running (slightly) outdated clients.

Thanks for TSVN,

Best,
Magnus

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1099677

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

[Simon Large]

2009/2/4 Magnus ... <acc...@zulutime.net>:

> I'm sorry if this has been mentioned before and decided against on
> architectural grounds. But it seems to me that it might make life
> easier for a lot of people if the TortoiseSVN installer could
> (optionally) install the CLI tools svn/svnadmin/etc along with the
> TortoiseSVN binaries and (optionally) set the path to include the
> TortoiseSVN directory.

It was mentioned last week on the dev list:
http://groups.google.co.uk/group/tortoisesvn-dev/browse_thread/thread/79f5e6798ae5f2e7#

> In my case, TortoiseSVN is my main client with 95% of repository
> access occurring through TSVN. However, a few times I need to use a
> CLI feature, so I need to ensure that every time I update, I update my
> CLI install at the same time (I'm using SlikSVN, without Apache
> bindings, for that). Add to that the fact that TSVN helpfully includes
> plink to allow svn+ssh connections right out of the box and the
> benefits become even more obvious and pronounced.
>
> The extra hassle of making sure I match both programs on upgrade
> actually means that I upgrade much more seldom than I otherwise would
> and end up running (slightly) outdated clients.

You don't need to keep the versions in sync for every last point
release. Sure, 1.4.x working copies are incompatible with 1.5.x, but
1.5.0 is compatible with 1.5.7.

Simon

--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1101127

[Bob Archer]

> The extra hassle of making sure I match both programs on upgrade
> actually means that I upgrade much more seldom than I otherwise would
> and end up running (slightly) outdated clients.

I think the biggest issue here is that these tools don't rev together.
So, just because TSVN has an update doesn't mean there is an svn CLI
update and vice versa.

Also, this would make the d/l bigger.

As long as you have the same Major.Minor version of each tool the
working copy will be compatible to both versions. So, you can have 1.5.6
of TSVN and 1.5.3 of svn and be good to go.

BOb

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1102593