On Mon, 23 Aug 2004 10:38:55 +0200, Marc Guenther <firstname.lastname@example.org> wrote:
> I just looked at the fink package 'svn-ssl-javahl' and it includes a
> libsvnjavahl.jnilib also. Its in /sw/share/java/svn-ssl-javahl/. But it
> seems its not included in the 'java.library.path' by default (anybody
> knows how to set this property systemwide ?).
i have no idea what the equivalent to ld lib path is on osx (or if
there even is one). i recall reading somewhere that when installers
say "optimizing disk" they are really scanning the whole system to
find libs to pre-link. some sort of OC deal. obviously i'm not
expert on this.
> So now I don't understand. Why actually IS subclipse so picky about
> which version of subversion is installed? Why can't it just use the
> ..jar and .jnilib thats already installed, instead of bringing its own.
> I understand that the low level jni api is changing frequently, but
> certainly not the high level java api ?!?
because by default, the svn builds on linux and osx don't build javahl
at all, and until very recently, getting javahl compiled _period_ was
very very difficult (very strict requirements on automake and such).
explaining to users how to install the right version of svn is much
easier than getting users to compile the thing from scratch. clever
people such as yourself will figure it out in the end anyway :)
i don't think there really is a good solution to this problem (though
there are several that are better than what we're doing). that's why
it's called dll hell i think.
Received on Mon Aug 23 23:29:09 2004