I'm sponsoring a (contrib) package that depends on java2-runtime. I (as a user of the package) will have to install the Blackdown VM to make it work, but I still want other java programs to use Kaffe because it's free. Pointing the "java" alternative to Kaffe will break the package, though ...
So I propose the following addition to java-policy: Providers of "java2-runtime" must also provide a "java2" alternative. Packages depending on "java2-runtime" can use this to be sure to get a java2-compliant environment. This allows for different defaults for java1 and java2 environments. The same could apply to "java2-compiler" and "javac2", but I'm not sure if that is too useful (what *are* the differences between java1-compiler and java2-compiler, exactly?). -- Robbe
signature.ng
Description: PGP signature
