Hi, On Tue, 2004-08-31 at 04:12, Grzegorz B. Prokopski wrote: > Not sure it's a good idea. Given that the "java-virtual-machine" > dependency was created to accomodate the properties shared among > the JVMs and that most of JVMs, in general, is capable of running > JNI code, running a JNI code is kind of expected from a package > that provides "java-virtual-machine". > > Additionaly there's no automatic or even semi-automatic way to > ensure that ikvm won't be used to run some java code using JNI > libraries. This is bad as there is plenty of java libs that > contain some (usually minimal) native part. The best that can > be done is to go case-by-case and add " | ikvm" do Depends: of > these packages that can be effectively run with it. Note that the new IKVM snapshot (from today) has a new JNI provider which should be at least good enough to get Eclipse 3 starting up. So it should now be at least as capable as jamvm, gcj/gij or kaffe with respect to JNI. Cheers, Mark
Attachment:
signature.asc
Description: This is a digitally signed message part