On 07/29/2014 05:24 PM, Florian Weimer wrote:
On 07/29/2014 04:59 PM, Omair Majid wrote:
>>> Then the most simple way is to provide symlinks in
>>> java-1.{7,8}.0-openjdk spec
>>>
>> >from /usr/lib/jni | /usr/lib64/jni, -to> /usr/lib/jvm/java..../... ?
>
>> Is it a good idea to install files from RPMs through a symbolic link?
>
> We could use the alternatives mechanism for this.
How so and why?
Because you caninstallmultiple jdks in time,and you are switching among them via
alternatives.
The alternatives already covers jre/sdk dir, jcm exports dirs and all jre/jdk binaries
llike java
(and its slaves) or javac (and its slaves)
So unless you wont to have /usr/lib{,64}/some-sepcific-jdk-version1-jni
/usr/lib{,64}/some-sepcific-jdk-version2-jni and so on, you have to control thos elinks in
same way
as bianries.
Maybe solution may be to have those /usr/lib{,64}/some-sepcific-jdk-version1-jni ... and
have
master switching link of /usr/lib{,64}/jni pointing to right (via alternatives selected)
/usr/lib{,64}/some-sepcific-jdk-version1-jni
>> I
>> suspect it's not, which would mean we'd have to use the upstream default
>> "/usr/java/packages/lib/amd64" in spec files (probably using a macro).
If
>> that path is acceptable, it would be fine with me as well, but it looks a
>> bit ugly to me.
>
> We can change (add and remove from) this path in the JDKs that we ship,
> if we have to.
It would be nice to preserve compatibility with proprietary JDKs, too.