--- Comment #4 from jiri vanek <jvanek(a)redhat.com> ---
(In reply to Michael Simacek from comment #3)
(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
But that assumption is 99% correct. There was sucesfull effort to make packages
to require jsut "java"
package that is doing that. What if a packager of something deep in
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.
That is slightly different case. If some of my depndencies pulls it in, that
its on discussion with maintainer how to make it work. The dependence tree is
quite shallow and the most used depndencies are usually most healthy.
Unluckily, all java packages requires JP. So by enforcing this here you are
affecting them all.
Do you mind to stop asking quite unrelated questions and get back to the issue?
Would be nice focus why JP are requiring suddenly java-1.8.0-openjdk and
mayhem it brought.
You are receiving this mail because:
You are on the CC list for the bug.