but, let me repeat my question:
it seems that other (professional) subversion clients (e.g., the one in the
upcoming IDEA release) completely rely on JavaSVN. Why not go that way with
suclipse as well? Or, at least provide a default JavaSVN config under Linux
that is completely independent of any binary stuff?
Zitat von Mark Phippard <MarkP@softlanding.com>:
> Russel Winder <email@example.com> wrote on 07/20/2005 03:55:18 AM:
> > Clearly this is a package maintainer thing so it is really down to the
> > Subclipse management and the JavaHL people to negotiate with the
> > Subversion package maintainers to get things organized sensibly.
> Subclipse "management"? I got a chuckle out of this. Also, there are no
> "JavaHL people". JavaHL is an official part of the Subversion project. So
> the "JavaHL people" are just the Subversion devs. The problem is that
> they do not view binary packages as part of their "domain". In fairness,
> they have done a lot of work to make JavaHL easy to build and that is
> starting to encourage the downstream maintainers to support it. There are
> now Debian packages that support JavaHL, and the RedHat RPM can be tweaked
> to support it. As I understand things, a big part of the problem is that
> to build JavaHL you have to have Java, and most distros will not provide
> packages for anything that requires Java because of the whole open source
> issue. That is also starting to get better as some open source Java
> compilers, such as the Eclipse compiler, have started to emerge.
> The next problem is that we cannot just build and distribute a JavaHL
> library for Linux ourselves, at least not easily. The way Subversion is
> built there are just too many dependent libraries. It might be possible
> to bundle all of them, but doing do in a way that does not cause other
> problems seems unlikely. The JavaHL library can be built statically, but
> as I understand things from previous posts, the way that Java loads a
> library via JNI somehow "ignores" that (uses ldd?) and forces the
> dependencies to be loaded dynamically.
> Ideally, we could build the JavaHL library statically, so that we knew we
> had all of the dependecies we needed, and then we could somehow do some
> magic in Java that would let that library be loaded, as a static library.
> If that could be done, then we could probably include a Linux binary.
> 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 Wed Jul 20 23:38:43 2005