Currently mk/java-vm.mk allows USE_JAVA2 to be be set to any of: "yes no 1.4 1.5 6 7 8 9 17" 1) I'd like to remove "9" and add "11" The current LTS java versions are 8, 11 and 17. No-one should be using java9 now, and pkgsrc no longer includes a java9 implementation 2) I'd like to remove "1.4" as we do not provide a 1.4 JVM 'nuff said 3) I'd like to adjust the semantics and rename it to JAVA_VERSION Currently USE_JAVA2 implies java 1.4 or later (effectively 1.5 given our jdk availability). I'd like to adjust it to be an actual JDK version, so all of the packages using "USE_JAVA2=yes" would get "JAVA_VERSION=1.5". Also would add a 1.1 option which would be the default, as we technically _do_ provide a java 1.1 JVM in the form of kaffe. While it is dissimilar to python and similar as a higher JVM should be able to run anything built by a lower one (hand waving away issues _building_ ancient java code needing java8 or earlier as we do not appear to have any of that in pkgsrc), this use of JAVA_VERSION seems less confusing than USE_JAVA2. Happy to make this JVM_VERSION= or JAVA_JVM= or similar if people feel that would be better naming. Would obviously update pkgsrc and wip packages. Changes for "1)" (the simplest) attached For reference the current Package-settable variables: # USE_JAVA # When set to "yes", a build-time dependency on the JDK and # a run-time dependency on the JRE are added. # When set to "run", a run-time dependency on the JRE is added. # When set to "build", a build-time dependency on the JRE is added. # # Possible values: yes run build # Default value: yes # # USE_JAVA2 # When the package needs a Java 2 implementation, this variable # should be set to "yes". It can also be set to "1.4", "1.5", "6", # "7", "8", "11" and "17" require an even more recent implementation. # # Possible values: yes no 1.4 1.5 6 7 8 11 17 # Default value: no # # PKG_JVMS_ACCEPTED # The list of JVMs that may be used as possible implementations. #
Attachment:
diff
Description: Binary data