2009/2/4 Magnus ... <account_at_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:
> 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.
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-02-04 10:38:03 CET