Re: implementing sensible-java to improve the alternative system
Hi Matthias,
let me answer in a different order.
> What does the name 'sun' mean? A vm, a jdk, anything else? If it's a VM, it better should be something like hotspot, zero, zeroasm, or shark.
It is currently inspired by java-wrappers but need not be identical to
java-wrappers. I am open for suggestions. Java-wrappers defines sun as
# all sun runtimes
__jvm_sun="$__jvm_sun4 $__jvm_sun5 $__jvm_sun6"
# Sun runtimes
__jvm_sun4="/usr/lib/j2*1.4-sun"
__jvm_sun5="/usr/lib/jvm/java-1.5.0-sun /usr/lib/j2*1.5-sun"
__jvm_sun6="/usr/lib/jvm/java-6-sun /usr/lib/j2*1.6-sun"
# Sun version at least 5:
__jvm_sunmin5="$__jvm_sun5 $__jvm_sun6"
> improving the current alternative-based system is needed, but you only replace one inflexible system with another one.
That is intended somehow. Java-common should not be updated too often
and that is why the flavor mapping is based on directory names that do
not change often.
> - no choice of a specific VM
> - no choice of compiled or interpreted mode
Is the information easily available in the JDKs?
> While the java world seems to be most ix86 centric, IMO a distribution
> should try to support java on all it's supported architectures. This
> might include working around jvm issues on specific architectures.
May you add a use case to the Wiki page
<http://wiki.debian.org/Java/SensibleJava>? That would make it easier to
understand your issue.
Cheers,
Torsten
Reply to: