Bug#212863: new java policy: ok or not?

[Jan Schulz <jasc.usenet@gmx.de>]

Hallo Ben,

* Ben Burton wrote:
>My only comment is that since sarge is purportedly so close to freeze
>and since this is more or less a complete policy rewrite, I think we
>should keep current java policy until after sarge.

Yes, thats sensible.... :) Anyway, as I stated, I can't see a problem
in implementing the new behaviour. Apart from a few packages, it will
be something like 

if [ -x /usr/bin/findjava ] ; then
  POSSIBLE="kaffe sun-java-1.4 ..." ; 
  JAVACMD="$(findjava -client $POSSIBLE)";
fi 
if [ "$JAVACMD" = "" ] ; then
   # current magic to find a java
fi
if [ -x /usr/bin/java-config ] ; then
  PACKAGES="...."
  CLASSPATH="$(java-config --all $PACKAGES)";
else
   # current classpath magic
fi   

>I'm perfectly happy to have the scripts/etc in java-common/etc now, as long
>as they don't interfere with current behaviour and current policy.

So that's one :)

Jan
-- 
Jan Schulz                     jasc@gmx.net
     "Wer nicht fragt, bleibt dumm."