F22 System Wide Change: Legacy implementations of the Java platform in Fedora

Severin Gehwolf sgehwolf at redhat.com
Tue Feb 24 12:34:18 UTC 2015


On Tue, 2015-02-24 at 12:43 +0100, Mikolaj Izdebski wrote:
[...]
> > ==== option one - introducing new packages - preferred ====
> > 1. main jdk is proclaimed as dead as it was until now.  The new jdk is derived 
> > as new package prviousName-legacy
> 
> Fedora already supports multiple JDKs installable in parallel. This was
> inherited from JPackage project. This breaks long-established rule of
> naming JDK packages as "java-x.y.z-vendor" used across different
> distributions (JPackage, Fedora, RHEL, SUSE, ...)
[...]

The idea behind this "-legacy" suffix was to ensure a reasonable upgrade
path for people *only* using default java-x.y.z-openjdk package. 

Consider the following scenario (all hypothetical, not saying that any
Fedora releases and JDK releases align in this way):

F22 has default JDK of java-1.8.0-openjdk. Then, F23 will get
java-1.9.0-openjdk as default and F24 java-1.10.0-openjdk as default.
The upgrade from F22 => F23 will install java-1.9.0-openjdk and remove
java-1.8.0-openjdk. Similarly, the upgrade from F23 to F24 will install
java-1.10.0-openjdk and remove java-1.9.0-openjdk. This is to ensure
that no old JDKs stick around on the majority of Fedora systems.

If the name was kept there does not seem to be a good way to:
1.) Ensure dist upgrades update JDK packages
2.) Ensure dist upgrades remove old JDK package (which may no longer
    get security updates).

Do you see a way to achieve this without a name change of the package?

Cheers,
Severin


> -- 
> Mikolaj Izdebski
> Software Engineer, Red Hat
> IRC: mizdebsk





More information about the devel mailing list