On Wed, Jan 22, 2003 at 02:20:54AM +1100, Ben Burton wrote: *SNIP* > > As an aside, it's also worth noting that even if package dependencies > become so restricted that they end up depending on a single JVM, having a > package depend on a specific JVM doesn't at all imply that that specific > JVM will be called when your startup script runs /usr/bin/java, and > hardcoding a specific JVM in your startup script removes the whole > point of being able to choose between different free and non-free JVMs. > For this problem I again point to the JVM registry that I've mailed about > several times on this list (and even wrote an initial implementation for), > that people have said looks nice and then that has been summarily ignored. :)
I know, I know. I should take a look at this sometime. Is it possible for you to either package it separatly (for testing purposes, maybe outside sid?) so people can see if it works nice and what the problems are. You can put the files in /usr/share/java-common or similar to make it easier to integrate into java-common later. I just do not have the time to check such a beast right now. :( Regards, // Ola > b. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
