From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Julien Lepiller <julien@lepiller.eu>, guix-devel@gnu.org
Subject: Re: No default OpenJDK version?
Date: Tue, 16 Apr 2024 14:50:54 -0700 [thread overview]
Message-ID: <87v84h0yf5.fsf@wireframe> (raw)
In-Reply-To: <7E2D3637-9BD5-407A-8314-0C08A0D216B3@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 2465 bytes --]
On 2024-04-16, Julien Lepiller wrote:
> Currently, most java packages use the implicit jdk from the build
> system (ant- or maven-build-system), which is… icedtea@8. We still
> have quite a lot of old packages that don't build with openjdk9, so
> I'm not sure when we can update the default jdk…
But for the packages that explicitly need to pull in openjdk:
git grep 'openjdk[1-9]' | grep -v define-public | grep -v java.scm | nl
1 gnu/packages/android.scm: (native-inputs (list openjdk12))
2 gnu/packages/apl.scm: (inputs (list bash-minimal openjdk18))
3 gnu/packages/apl.scm: (native-inputs (list `(,openjdk18 "jdk") zip))
4 gnu/packages/axoloti.scm: `(("openjdk" ,openjdk11 "jdk")
5 gnu/packages/bioconductor.scm: (list (list openjdk11 "jdk")
6 gnu/packages/bioinformatics.scm: #:jdk openjdk11))
7 gnu/packages/cran.scm: ("jdk" ,openjdk11 "jdk")
8 gnu/packages/diffoscope.scm: (list `(,openjdk12 "jdk")
9 gnu/packages/emacs-xyz.scm: (list emacs-ecukes emacs-espuds emacs-undercover openjdk9))
10 gnu/packages/geo.scm: openjdk11))
11 gnu/packages/geo.scm: #:jdk ,openjdk11
12 gnu/packages/groovy.scm: #:jdk ,openjdk9
13 gnu/packages/groovy.scm: #:jdk ,openjdk9
14 gnu/packages/groovy.scm: #:jdk ,openjdk9
15 gnu/packages/groovy.scm: #:jdk ,openjdk9
16 gnu/packages/groovy.scm: #:jdk ,openjdk9
17 gnu/packages/gstreamer.scm: ("openjdk" ,openjdk14)
18 gnu/packages/gstreamer.scm: ("openjdk:jdk" ,openjdk14 "jdk")
19 gnu/packages/java-compression.scm: #:jdk ,openjdk9
20 gnu/packages/kodi.scm: openjdk9 ;like groovy
21 gnu/packages/mpi.scm: `(("jdk" ,openjdk11 "jdk")
22 gnu/packages/pep.scm: `(,openjdk9 "jdk") which yml2))
It is not a crazy number of packages, but in cases like diffoscope and
enjarify, which seem fairly compatible with arbitrary versions, it would
be nice to have an unversioned option to specify?
Maybe I confused things by talking about the "default" version, I guess
I was wondering if it would make sense for an "openjdk-latest" or
"openjdk-lts" or whatever color you want, just as long as it does not
require specifying (and more importantly, keeping track of) the version
of openjdk needed.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-04-16 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 20:25 No default OpenJDK version? Vagrant Cascadian
2024-04-16 20:37 ` Julien Lepiller
2024-04-16 21:03 ` Attila Lendvai
2024-04-16 21:50 ` Vagrant Cascadian [this message]
2024-04-17 4:58 ` Julien Lepiller
2024-04-20 17:19 ` Markku Korkeala
2024-04-21 5:31 ` Julien Lepiller
2024-04-22 17:32 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v84h0yf5.fsf@wireframe \
--to=vagrant@reproducible-builds.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).