-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel Veillard wrote:
| I would like something more flexible, to that end I added some JDK dynamic
| detection in configure.in for my package, which then allows to guess the
| jni.h and jni_md.h based on the javah and javac used to generate the
bindings
| (so things should stay consistent).
| In the spec file I used the following:
There is no need since java and java-devel are virtual Provides provided
by every compliant JDK, so the user is already allowed to choose the JDK
that they want to build with.
Also, there are macros that should be used when refering to the JDK so
that you pick up the default JDK used for building and not the current
default alternative (e.g., %{java_home}, %{java}, %{javac}, %{jar}).
Unfortunately, there are recent packages passing the Fedora review that
directly specify java-1.6.0-openjdk-devel as the JDK and I personally
don't like this.
I think that this comes from two schools of thought: one group wants to
tie the Fedora package even more tightly to Fedora and the other wants
to leave the options open. Since Fedora more-or-less has only one JDK
(or two counting GCJ which is optional), this benefit is mostly
theoretical, but you can see from the current discussion that it can be
useful. Similarly, since Fedora can force the default JDK setup at build
time through the build system, although the packages are technically not
as flexible as they could be, it's never really a problem in practice.
- --
Sincerely,
David Walluck
<david@xxxxxxxx>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org
iEYEARECAAYFAkhqWlAACgkQItObMyg2XCUpNgCghlrnFGtwJPikTBuBxLCCNLLe
3r0AnRs5bIeVxAruG1Ri/bkhQuYwY/63
=6Tqq
-----END PGP SIGNATURE-----
--
fedora-devel-java-list mailing list
fedora-devel-java-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-java-list
