Carlos Rodriguez-Fernandez wrote:
> How could that be expressed so that those are caught quickly at build
> time? Someone wants to depend on a java lib that has been tested only in
> JRE 8 to 11, but wants to build the package with JRE 17+, or vice-versa,
> for example. Perhaps, the only feasible way to detect that case is with
> CI.
IMHO, the library should have a:
Requires: (java-devel >= 1:8 with java-devel < 1:11)
Sure, this will not per se prevent you from attempting to use the library
with the Java 17 compiler, but if you do not have Java 8 or 11 installed,
installing the library attempting to install it as a dependency should raise
a red flag.
As a quick check, you could write a specfile for your application with:
BuildRequires: java-devel >= 1:17
BuildConflicts: java-devel < 1:17
and then run mock on that. The latter line should prevent the old version
from being installed in parallel.
One annoyance is that older OpenJDK packages currently drop that virtual
Provides, presumably in an attempt to get all Java packages systematically
built with a newer JDK. That is something that ought to get fixed. (If we
switch to building with the oldest possible Java as I suggest, it will have
to get fixed anyway.) As is, you may need to explicitly:
BuildConflicts: java-1.8.0-devel
BuildConflicts: java-11-devel
Kevin Kofler
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
