Stefan Gybas <[EMAIL PROTECTED]> wrote: > Jan Schulz wrote: > > > I'm currently using this line to get 'java' in debian/rules: > > jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3 > > /usr/lib/j2sdk1.3 > > JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \ > > then echo \ > > $$jdir;exit 0;fi;done) > > In eclipse? I think #197484 is a perfect example why this is bad and why > you should use one specific JDK version.
Most of my packages (not all) compile with j2sdk1.3 and 1.4. As 1.4 does not exist on powerpc, I am obliged to compile my packages on my office station... well, it's not really a problem (I read my mail at the moment on this station), but I think if someone want to build a package that can be built with 1.3 and do not have another JDK (because arch or else), he does not have to modify the build script. So I think I'll do something like: Build-Depends-Indep: j2sdk1.3 | j2sdk1.4 | java2-compiler and in debian/rules: jdk_dirs=/usr/lib/j2sdk1.4 /usr/lib/j2se/1.4 /usr/lib/j2se/1.3 /usr/lib/j2sdk1.3 JAVA_HOME ?= $(shell for jdir in $(jdk_dirs) ; do if [ -d "$$jdir" ]; \ then echo \ $$jdir;exit 0;fi;done) But there are, for sure, many differences between 1.3 and 1.4! I am really impatient for a _complete_ free implementation! -- Arnaud Vandyck http://alioth.debian.org/users/arnaud-guest/
