On Wed, 25 Aug 2004 16:06:57 -0400, Mark Phippard <email@example.com> wrote:
> So on Linux and Mac, javahl requires Subversion libraries to be installed,
> in addition to the ones required by Subversion like BDB? So this
> essentially means you probably need to have the command line client
> installed already? Also, in the case of the Mac, you couldn't use one of
> the popular static command line builds because then javahl would not have
> any libraries to load?
actually on *nix (mac included), javahl only requires the svn libs,
which in turn have their own set of dependencies. the bdb dependency
really lives in libapr, javahl really has nothing to do with it.
a static javahl is a funny animal, it needs to be dlopen()able, but
also be statically linked to its dependencies, something which a few
people hav figured out to do, and none have gotten integrated into the
To further complicate things, *nix javahl builds are currently broken
in rc2 due to a relink error on install.
Javahl is fun.
> I guess I come back to my opening statement, this is a complicated issue
> and it is hard to determine the ramifications. I think that by not
> shipping the libraries, you are probably just trading one set of problems
> for a new set which are currently unknown. Perhaps we should try to keep
> the system as is and instead try to recruit some voluteers to write good
> instructions for each of the three major platforms that discuss how to get
> a good setup and what the issues are?
maybe, maybe not. basically the windows case is the simple(r) one. the
real problems are in the unix builds.
Received on Thu Aug 26 06:20:13 2004