> Stefan Küng wrote:
>> Hmm - did you have to patch neon too? That's not included in the patch
>> on your website?
> No, it's not necessary to patch Neon sources, only it's buildfile (which is
> part of TortoiseSVN repository, I believe). You have to add several macro
> definitions (such as HAVE_GSSAPI) and paths to kerberos headers and
> GSSAPI32.lib. So the main problem, that I see with this patch, is that
But your patch doesn't set any defines or macros for neon?
It only sets the include paths and links to the lib, but I don't think
that's enough for neon to really use it.
> TortoiseSVN would not run without having MIT Kerberos dlls on PATH
> which...not everybody has. This issue has been discussed
> http://svn.haxx.se/tsvnusers/archive-2007-11/0135.shtml here .
> In order to make Neon load kerberos dlls dynamically, it would require
> patching Neon source.
> http://svn.haxx.se/tsvnusers/archive-2008-04/0248.shtml This discussion is
> about this more sophisticated patch and states that the author(s) of Neon
> refused to include it (I don't see their point and I have kinda anti-windows
> feeling of it).
> So I don't see a clear way to include GSSAPI/Kerberos support in the main
> distribution of TortoiseSVN. The argument, that it should be included in
> Neon, seems pretty clear to me. After all, that's why I decided to build the
> distribution myself...
I don't quite get what you did with your build. On your web page, you
mention that the saslGSSAPI.dll is needed, but SASL is used with the
svn:// protocol and neon is used with the http(s):// protocol.
Also, I've checked out the source from
svn://anonsvn.mit.edu/krb5/tags/kfw-3_2_2-final - but I haven't found
the build instructions yet...
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-05-15 22:19:10 CEST