Hi. Okay, so to be as tacky as to follow up to my own email: What if there were a specification in the java policy that all JNI modules are placed in /usr/lib/java/jni (or somewhere else appropriate beneath /usr/lib) and that each JVM be required to append /usr/lib/java/jni to its java.library.path? The reason I suggest this is that we already need to specify each and every jar that we use on the classpath (for which there are valid reasons), but having JNI stuff scattered in random locations means that there is then a slew of paths to add to java.library.path in addition to the jars. Now I can understand having to specify each jar to control what classes are available, but having to specify each JNI module as well seems redundant to me. This proposal means we keep stuff out of /usr/lib proper but (assuming the JVM plays along) everything is still transparent to the user or other program. So anyway. There you have it. Ben. -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] http://baasil.humbug.org.au/bab/ Public Key: finger [EMAIL PROTECTED] The only way to be rid of a temptation is to yield to it. - Oscar Wilde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
