3 ms·
Debian's stretch-backports had a slightly awkward transition phase where "openjdk-11" started as Java 9, then 10, and then 11... took about a month for it to ge
by chungy 8y ago
Debian's stretch-backports had a slightly awkward transition phase where "openjdk-11" started as Java 9, then 10, and then 11... took about a month for it to get "caught up". They did it because the JDK can be bootstrapped by version N-1, so building Java 11 required Java 10, which required Java 9 to build, which in turn required Java 8, which is the version in stretch anyway.
Though I doubt and hope Ubuntu didn't base their stuff on the backports branch...
- dcminter 8y agoThat seems odd to me - why could one not install (or build) package N-1 in order to build package N ? i.e. why does it all need to be the same package name?
- chungy 8y agoIt would have required moving openjdk-9 and openjdk-10 into backports only to be removed later. These packages were already removed from unstable and testing, and I assume it would have made things only more of a hassle... Also I guess it meant that installing openjdk-11 on stretch-backports would eventually gain you Java 11 (and it does now). I'm not a Debian maintainer. They'll probably have a better answer if you asked them :)