From Fedora Project Wiki
No edit summary
No edit summary
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->


Line 39: Line 35:
<!-- [[Category:SelfContainedChange]] -->
<!-- [[Category:SelfContainedChange]] -->
[[Category:SystemWideChange]]
[[Category:SystemWideChange]]
 
* System or Self contained change?  By the changes done, this is '''Self Contianed Change'''. However from view of impact, and possible world notification, it is more ''System Wide Change''.
* Targeted release: [[Releases/37 | Fedora Linux 37 ]]  
* Targeted release: [[Releases/37 | Fedora Linux 37 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
Line 62: Line 58:


According to short investigations, there are already precedents, where certification is a reason to build once, certificate, and repack.
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 ==
== Benefit to Fedora ==

Revision as of 11:49, 4 May 2022


Build all JDKs in Fedora against in-tree libraries and with static stdc++lib

This is a proposed Change for Fedora Linux.
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

Owner

Current status

  • System or Self contained change? By the changes done, this is Self Contianed Change. However from view of impact, and possible world notification, it is more System Wide Change.
  • Targeted release: Fedora Linux 37
  • Last updated: 2022-05-04
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

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 particualr 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 platfrom specific issues disappear, while JDKs remain same in view of system integration and user expereince

Scope

  • 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

How To Test

User Experience

Dependencies

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/JdkInTreeLibsAndStdclibStatic&oldid=643167"