Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.java > #12476
| From | Emmanuel Bourg <ebourg@apache.org> |
|---|---|
| Newsgroups | linux.debian.maint.java |
| Subject | Re: OpenJDK for Bookworm and beyond |
| Date | 2022-11-10 21:40 +0100 |
| Message-ID | <Fqmv8-2Q5s-11@gated-at.bofh.it> (permalink) |
| References | <FaYEp-aRp5-17@gated-at.bofh.it> <FmI1b-rr3-1@gated-at.bofh.it> <FmIaR-ru9-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Le 31/10/2022 à 19:54, Thorsten Glaser a écrit :
> No, we really should not: the various JDKs also only provide
> java<n>-runtime and this dependency is specifically meant to
> also make it possible for software to use a JRE *other* than
> the default (the dependency reads like
> default-jre (>= x) | javaX-runtime
> by design/for a reason).
That should also be possible with the versioned virtual package:
default-jre (>= 2:1.n) | java-runtime (>= n)
> Given how they stretch across versions and how many releases
> are supportable (ELTS from jessie on, *buntu from trusty on)
> I will argue that if and only if the openjdk-X source packages
> also start providing these _now_, that we can start switching
> to the versioned java-runtime provide in 2030, maybe later.
I agree the sooner the openjdk-<n> packages provide java-runtime (= n)
the better. But I don't see the need to wait a decade before using the
versioned java-runtime dependency in the packaged applications, what
issue do you foresee?
Emmanuel Bourg
Back to linux.debian.maint.java | Previous | Next — Previous in thread | Next in thread | Find similar
OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-09-29 12:10 +0200
Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-09-29 14:10 +0200
Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-09-29 20:10 +0200
Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-09-29 20:40 +0200
Re: OpenJDK for Bookworm and beyond Phil Morrell <debian@emorrp1.name> - 2022-10-12 02:00 +0200
Re: OpenJDK for Bookworm and beyond Moritz Mühlenhoff <jmm@inutil.org> - 2022-11-08 21:00 +0100
Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-08 21:00 +0100
Re: OpenJDK for Bookworm and beyond David Goodenough <david.goodenough@linkchoose.co.uk> - 2022-11-09 12:50 +0100
Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-10-31 19:50 +0100
Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-10-31 20:00 +0100
Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-10 21:40 +0100
Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-10 22:20 +0100
Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-10 22:50 +0100
Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-11 01:40 +0100
Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-11 01:50 +0100
Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-11 12:00 +0100
Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-11 16:30 +0100
Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-10 22:50 +0100
Re: OpenJDK for Bookworm and beyond Moritz Mühlenhoff <jmm@inutil.org> - 2022-11-08 20:50 +0100
Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-10 20:40 +0100
csiph-web