Re: F37 proposal: Build all JDKs in Fedora against in-tree libraries and with static stdc++lib (System-Wide Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/10/22 6:29 AM, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/JdkInTreeLibsAndStdclibStatic

This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==
This is initial step to move JDKs to be more like other JDKs, to build
proper transferable images, and to lower certification burden of each
binary. Long storyshort, first step in:
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs

This first step will move, one by one, individual JDKs in F37 to be
built `--with-stdc++lib=static` and against in-tree (bundeld)
libraries:  `--with-zlib="bundled"  --with-freetype="bundled"
--with-libjpeg="bundled"  --with-giflib="bundled"
--withlibpng="bundled"  --with-lcms="bundled"
--with-harfbuzz="bundled" `

We already made a heavy testing of the behavior, and user should not
face negative experience. I'm not sure if this is

I'm very confused on why this reduces certification burden. In our crypto libraries this is exactly the kind of behavior we would *NOT* want packages to do because it increases our certification and support burden.

bob


== Owner ==
* Name: [[User:jvanek| Jiri Vanek]]
* Email: jvanek@xxxxxxxxxx


== Detailed Description ==
Please see https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs
for whole picture

Please see https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Move_JDKs_in_RPMs_to_become_portable
for this particular step. I would rather keep the details  in the main
page then here.

== Feedback ==
According to short investigations, there are already precedents, where
certification is a reason to build once, certificate, and repack.

According to developers, the non-portbale JDK is  causing upredicted
behavior different from other JDK vendors

According to JDK packagers and testers, there is to much JDKs now, and
the https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Move_Fedora_JDKs_to_become_single-built.2C_portable.2C_ordinary_JDKs.2C_while_keeping_comfortable.2C_usual_system_integration
  is the only way out

== Benefit to Fedora ==
Please see https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Motivation
for whole picture.

This particular proposal's main benefit will be that Fedora's JDKs as
packed in RPMs will again start to resemble upstream JDKs and other
vendors build, and some platform specific issues disappear, while JDKs
remain same in view of system integration and user experience

== Scope ==
* Proposal owners: push improved version of
https://src.fedoraproject.org/rpms/java-latest-openjdk/pull-request/98#request_diff
to all JDKs - one by one from latest, over 17 to 11 and 8. Once
settled down in F37 the backport to F36 is expected.

* Other developers: really, nothing. If there will be unexpected
impact to other developers, the
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs may
need rework

* Release engineering: N/A [https://pagure.io/releng/issues #Releng
issue number]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:


== Upgrade/compatibility impact ==
The compatibility and upgrade path should remain completely smooth.


== How To Test ==
Install system JDK (java-17-openjdk) and ru your favorite application
or development. No regression should be noted.


== User Experience ==

Because of in-tree  libraries, minimal image or font rendering
differences canbe spotted after very detailed investigations -
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Side_effects
- still, no of th e
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Known_issues
should be hit by this proposal.


== Dependencies ==
No dependent packages should notice the change.


== Contingency Plan ==
* Contingency mechanism: Revert the patches and rework
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs
* Contingency deadline: before f37 release
* Blocks release? Unless the java-stack will become completely borked then no.


== Documentation ==
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs



_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux