All: Current Debian Java Policy [1] in section "Chapter 2.1: Virtual Machines" stipulates "If a virtual machine supports native code, it must include the directory /usr/lib/jni in its search path for these dynamic libraries."
There is no rationale given for this policy choice and I fail to see the advantage of it. On the other hand I can imagine the following contraindications: - Multiple VM's, or different versions of the same VM, may use similarly named native libraries which have different version dependencies. In the aforementioned policy scheme there is no way to avoid such a version clash. - Each VM under /usr/lib/jvm/<vm-name>/ it would seem should be self contained in that file hierarchy, insomuch as possible. - Usually VM native libraries are required to implement the VM itself and would not have any utility being exposed in a "public path" as a native Java add-on library would Shall this requirement be dropped for virtual machines? Regards, --Tom [1] http://wiki.debian.org/Java/Draft _____________________________________________________________________________ [EMAIL PROTECTED] Senior Java Performance Engineer Sun Microsystems, Inc. http://blogs.sun.com/tmarble What do you want from Java Libre? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
