F22 System Wide Change: Legacy implementations of the Java platform in Fedora
jvanek at redhat.com
Thu Feb 26 08:34:58 UTC 2015
On 02/26/2015 09:16 AM, Mikolaj Izdebski wrote:
> On 02/25/2015 06:58 PM, Miloslav Trmač wrote:
>>> On 02/24/2015 06:41 PM, Miloslav Trmač wrote:
>>>>> "java" would be the preferred JRE in Fedora. The package would have no
>>>>> content, but it would have Requires on preferred Fedora JRE, currently
>>>>> java-1.8.0-openjdk. This could be easily changed as default JRE changes.
>>>>> The same is for other binary subpackages of "java", respectively.
>>>>> All system packages would require subpackages of "java" as they do now
>>>>> (unless there is good reason not to). Users that install "java" would
>>>>> get latest JRE, which would be updated to new major versions as they
>>>>> become default. Older JDKs would not be removed during update (unless
>>>>> there is no maintainer and they are obsoleted as currently),
>>>> AFAIK nothing obsoletes a package just because it is orphaned…
>>> If no volunteer shows up for maintenance of old JDK then it would be
>>> deprecated and obsoleted, as it's was done with previous JDK packages.
>> How would that work _exactly_?
> 1) JDK maintainers announce deprecation in advance and call for
> volunteers to maintain old JDK
> 2) when the time of deprecation comes, JDK package is reassigned to new
> maintainer, if such showed up; no obsoletes are added
This is heavily untrue. The obsolete (or similar mechanism) is necessary.
We do not wont any user to live unvoulenteerly and unwillingly with legacy jdk. I would like also
to avoid just keeping the legacy jdk on his drive.
1- the stack will eb compiled by nex (newr) jdk - so old jdk will not be bel tun it.
- even keeping it on drive may lead to risk of usage it (speaking about basic user here). Not
speaking about vasting of space on drive after several major updates.
2- low mainatainance. The community maintained jdk can never be expected to be so uptodate == so
safe asmain jdk, which is mainatined by openjdk upstream-working people.
> 3) if there is no new maintainer then old JDK is redired in pkgdb,
> blocked in koji and obsoleted by some other package
> 4) if maintainer shows up after old JDK was retired then he can just
> revive package (passing review if needed); package release is bumped to
> be higher that obsoletes
More information about the devel