Hallo Mark,
* Mark Johnson wrote:
>In the past, I've simply used /usr/bin/java or /usr/bin/gij (saxon-catalog),
>but have had bug reports filed against the package because it breaks with
>policy.
>In short, can you tell me the 'correct' options as far as interpreters are
>concerned? (Actually, _any_ help would be appreciated!)
There is none. Debian java policy doesn't yet handle the problem with
one JVM can run and others can not run a java app. Thats why we had
the big discussion about a month ago.
/usr/bin/java can be anything from IBM1.1 over sablevm and kaffe to
SunJDK1.4. My advise (highly biased :) try to get your app working
with kaffe or gij and call them directly. The other choice is to use
/usr/bin/java (which is current policy) and wait for the bugreport,
that your app can't be run on the users system.
Or wait for a policy change :) In that future, you will have to name
all JVMs, which work and add them to your Depends and to a call to
'findjava' (all done via some debhelper command) and that script will
figure out the right start command.
Jan
--
Jan Schulz [EMAIL PROTECTED]
"Wer nicht fragt, bleibt dumm."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
