On Wed, Jul 07, 2004 at 03:09:35PM +0200, Rafael Laboissiere wrote:
> * Andrew Ross <andrewross@...> [2004-07-07 08:56]:
> > But kaffe is a dummy package as well, ensuring one of kaffe-pthreads
> > or kaffe-jthreads gets installed. Both kaffe-pthreads and kaffe-jthreads
> > provide java-virtual-machine, java-runtime, java1-runtime, java-compiler,
> > kaffe.
> Oops, I have not noticed that kaffe was a dummy package. Thanks for the
> heads up.
> > We don't need the kaffe dependency. Let's go with
> > Depends: java-runtime1
> > Recommends: java-compiler
> > Obviously java-compiler is a build dependency. We also need jar. There
> > doesn't seem to be a virtual package for that so we will have to explicitly
> > add fastjar | kaffe as a build dependency I guess.
> A build-dependency on libgcj4-dev | kaffe-dev is also needed in order
> to have the jni.h present in the system.
Good point. libsablevm1-dev also supplies it.
Sigh... This kind of defeats the whole point of using java-compiler. Oh
well... I guess java policy still has some way to go.
> > (I think kaffe provide jar according to packages.debian.org. Can you
> > confirm this Rafael, I'm running testing not unstable.)
> > I think java1-runtime is the right dependency rather than just
> > java-virtual-machine since we need the java classes as well as the
> > actual interpreter. Java 1 is fine for our needs.
> Do the PLplot Java bindings work with a Java 2 interpreter? In this case,
> we could use java1-runtime | java2-runtime instead.
I can see no reason it shouldn't work with either. It's all pretty noddy
java really. Though currently testing has no java2-runtime packages.