Re: /usr/lib/jni support in Fedora

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/04/2014 12:38 PM, Florian Weimer wrote:
> On 07/30/2014 11:39 AM, Andrew Haley wrote:
> 
>> Ideally we'd want to have this discussion with Java upstream.
> 
> Okay, I can bring it up there, but I'm not sure yet what Fedora's needs 
> are, so I think it's premature to bring it up upstream.

I agree.

>> Depending on a Fedora-local patch to the search path means that if
>> people build their own OpenJDK or install Oracle Java, their programs
>> will stop working.  So, we must not do that.
> 
> I suspect that using a JDK not packaged by us needs a changed invocation 
> of the launcher anyway,

I don't see why it needs to, and IMO we should strive to ensure that
it does not.  JAVA_HOME is traditional but fugly, and doesn't work
properly with alternatives.

> and throwing the appropriate 
> -Djava.library.path= setting would only be a minor complication, 
> compared to all the other things that aren't quite right by default.
>
>> If a symlink at /usr/java/packages/lib/amd64 to wherever is allowable,
>> and I see no reason why it should not be, then we don't need to patch
>> OpenJDK.  We could make /usr/java/packages/lib/amd64 a real directory,
>> and populate it with symlinks to the packages or make it just a
>> symlink to /usr/lib64/jni ; again, I don't think it matters.
> 
> If there's consensus to introduce /usr/lib64/jni with compatiblity 
> symlinks under /usr/java/packages/lib, then we don't need any upstream 
> changes, just a java-filesystem package which installs the symbolic 
> links, and a change to the Java packaging guidelines.

Indeed.  It's a simple solution that will work, not only with future
JVMs but with existing ones.

> Debian uses (or will soon use) multiarch paths, and these seem
> difficult to compute outside of a Debian environment, which is why I
> believe that changing the upstream default to include appropriate
> /usr/lib/jni directories could be challenging.  Maybe we could just
> use the non-multiarch directories, and Debian can keep patching the
> defaults, but that doesn't seem ideal to me, either.

Debian's multiarch system is a can of worms, and whatever they do with
it won't be ideal.  They'll always need to patch, I think.

Andrew.
--
java-devel mailing list
java-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/java-devel





[Index of Archives]     [Red Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux