On 02/26/2015 09:31 AM, Aleksandar Kurtakov wrote:
----- Original Message -----
From: "Mikolaj Izdebski" <mizdebsk@xxxxxxxxxx>
To: devel@xxxxxxxxxxxxxxxxxxxxxxx
Sent: Thursday, February 26, 2015 10:16:26 AM
Subject: Re: F22 System Wide Change: Legacy implementations of the Java platform in Fedora
On 02/25/2015 06:58 PM, Miloslav Trmač wrote:
On 02/24/2015 06:41 PM, Miloslav Trmač wrote:
Hello,
"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
We speak about people that are already Fedora packagers, right? Just sponsoring someone that showed up and let him/her maintain
Still it is possible scenario.
I can even guess that this person will be apckaging newbe - most of java developers do not care
about packaged stuff below. They have theirs Java EE and are happy that packages are solving all the
issues they dont like.
On contrary, if such a person wonts to pack it then you cna expect him to learn quicly.
> legacy JDK in Fedora is recipe for disaster.
Thats what this guidelines should prevent...
For not-yet-packagers they would have to go through the full review-sponsoring process.
Alexander Kurtakov
Red Hat Eclipse team
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
--
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
