> If you have better definitions on how to define java1-runtime and/or > java2-runtime, I'm grateful for such propositions.
If AWT / GUI stuff is a particular problem (which is my understanding), I think it would make sense to define virtual packages java1-awt-runtime (and possibly java2-swing-runtime). This way we can have kaffe provides java1-runtime, java1-awt-runtime and sablevm provides java1-runtime (without the awt virtual package). This way non-GUI apps can depend on java1-runtime and be installed against a multitude of free JVMs, whereas GUI apps can restrict their dependencies to those JVMs that support AWT/Swing. Though of course there's no guarantee that /usr/bin/java actually points to the AWT-capable JVM if you have several JVMs installed. Though this is a slightly different issue. b. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
