If it were possible to convert to a "DLL-based" packaging, that might make
adding the command line not too big. Hard to say though, since when
Subversion moved to using APR DLL's that did not seem to make things
My main interests are:
1) Single copy of dependency DLL's, mainly because of the compiler issue
and the dependencies it adds.
2) Single install location. This is really related to #1. I would hope
if everything was in the same place the problems related to the MSVC
runtimes would go away. I would like to see the bindings like JavaHL
available for same reasons.
3) Single code base. Unfortunately, TSVN has to make some patches to
Subversion for optimal Windows performance. It would be nice to have those
in the CLI as well.
4) If TSVN features like the local password encryption could work from the
CLI because of this, that would be cool. Not sure if it would.
5) I know Stefan has made some optimizations to APR Iconv. I have never
quite understood what the ramifications of these are, but again perhaps
would bring some benefits to the CLI.
Binaries are not an official deliverable of the Subversion product. They
have been kind enough to produce and host them for us Windows users. I
just think Stefan and Tortoise with their obvious knowledge of how to do
Windows right could do this better and become the official Windows
Like I said, I am not really expecting Stefan to go for this, although I
wish he would consider it. I would, however, at least be interested on his
thoughts on the feasability. There is no reason someone else couldn't
assemble and provide all of the pieces as well. I suspect Stefan has
explored some of the underlying issues in the past and knows what the
hurdles are that have to be overcome.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Sep 26 11:10:23 2004