Path names of native code files

[Mark Reinhold]

> Date: Tue, 02 Mar 2010 08:34:04 -0800
> From: mandy.chung at sun.com

> Per the module-file format spec v4 [1]:
> 
> "The path names of native-code files must not include more than one element."
> 
> The jdk currently contains files that are in deeper directory hierachy
> e.g. lib/i386/client/libjvm.so
>     lib/i386/server/libjvm.so
> 
> What is the rationale behind the pathname limitation?

Simplicity.  If we need multiple levels then let's make sure we have a
really good reason for them.

In the case of libjvm.so, for now those are in the base image, which we
are not yet delivering as a module file, so they can stay where they are
if that's easiest.

For other cases we should eliminate the $ARCH element since module files
will eventually contain architecture information for native code.  That
would leave just a few odd subdirectories (jli, xawt, headless) which I'm
pretty sure we can eliminate by modifying runpaths and/or using dlopen().

- Mark