--- Comment #3 from Michael Simacek <msimacek(a)redhat.com> ---
(In reply to jiri vanek from comment #2)
(In reply to Michael Simacek from comment #1)
> > It kills .* in buildroot
> Can you be more specific? What do you mean by kill?
If you require java 9, you expect it would be the only java in buildroot.
That assumes that none of the packages in the transitive closure of your
dependencies doesn't require any specific JDK. And jp is not the only package
that is doing that. What if a packager of something deep in your dependency
chain decides to add Requires: java < 1:9, because his pkg doesn't work with
java 9 yet? Relying on absence of a package is fragile. If people want to use
non-default JDK, they should make it explicit (by using JAVA_HOME).
However, suddnely you have also jdk8 in buildroot, and it will
alternatives on itself. And alternatives are the only thing we support for
You can workaround it by using /usr/lib/jvm/java-9 path, but then you lost
simple movability to another jdk.
> If some package needs to be built by different JDK than the default one, it
> can point JAVA_HOME to it.
Can and can not. JAVA_HOME is being discouraged (not only) in fedora for
long time. Well heavily used anyway for good reason.
Discouraged where exactly? By whom?
> As for java-1.8.0-openjdk-aarch32, if it should be the default for arm, we
> can change the Requires for that platform.
I don't know. The aarch32 port is not exactly super stable. And I do not
wont to rob user for choice. Well and that is what you did.
You are receiving this mail because:
You are on the CC list for the bug.