Re: implementing sensible-java to improve the alternative system
On Sat, May 8, 2010 at 6:20 PM, Matthias Klose <doko@debian.org> wrote:
> then sensible-* seems a waste of resources. maybe you could come up with a
> rationale first, what you do want to achieve?
Have you read the wiki page?
"All java related tools such as java, javac, javadoc are symlinks are
handled by the alternatives system. Neither the non-privileged user
nor the Debian packager can easily override which JVM should be used."
That is similar to sensible-browser, sensible-editor, or
sensible-pager. As one extra goodie it allows setting up the CLASSPATH
in a more comfortable way.
> afaik, no. it's VM information. -X and -XX options depend on a specific VM.
The existing sensible commands don't have any knowledge about specific
tools, e.g. ensible-editor does not support any options that are
specific to emacs, vim, ed, mcedit, ...
> well, the use case is selection of a VM (might be another path, or just
> another option), selection of VM specific flags (-XX, Xint, -Xcomp, ...)
> depending on architecture and application. Compare that with working around
> compiler bugs for some architectures with setting CFLAGS in the rules file,
> and using workarounds for architecture specific problems in the JIT
> (hotspot, shark).
Are there any options that are common for all types and versions of
JVMs on all architectures? Even if the JVM has been installed locally
instead of using a Debian package?
Cheers,
Torsten
Reply to: