From Fedora Project Wiki
(Created page with "<!-- 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 --> = ...")
 
(Scope)
Line 63: Line 63:
 
** (optional) Mass-change spec files that have "Requires: java" to "Requires: java-headless"
 
** (optional) Mass-change spec files that have "Requires: java" to "Requires: java-headless"
  
* Other developers: (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
* Modify spec files to have "Requires: java-headless" instead of "Requires: java"
 
* Modify spec files to have "Requires: java-headless" instead of "Requires: java"
  
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Release engineering:  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
 
** mass rebuild is not necessary but it would simplify things
 
** mass rebuild is not necessary but it would simplify things
  
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Policies and guidelines: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 
** [Packaging:Java] needs to be modified to account for java-headless package existence
 
** [Packaging:Java] needs to be modified to account for java-headless package existence

Revision as of 17:00, 29 October 2013


Headless Java

Summary

Server installations of Fedora should usually not pull in packages related to X system or sound subsystem. For this reason part of OpenJDK package has been split into headless subpackage which has smaller dependency chain. Fedora packages should be migrated to require java-headlesss instead of full java package when appropriate.

Owner

Current status

  • Targeted release: Fedora 21
  • Last updated: (DATE)
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

OpenJDK package in Fedora has been traditionally monolithic, pulling in a lot of dependencies including (but not limited to)

  • libXrender
  • libXi
  • libXtst
  • pulseaudio

This is obviously not optimal for minimal server installations where OpenJDK is used for web application development and deployment.

Designed after Debian packaging, Fedora OpenJDK package has been split into packages providing java and java-headless. This makes it possible for packages to use "Requires: java-headless". For most libraries and generic packages this is sufficient. End-user applications should keep "Requires: java" to pull in full OpenJDK package.

This change aims to convert most Java packages to have "Requires: java-headless" when appropriate. BuildRequires are unaffected.

Benefit to Fedora

  • Significantly smaller installation size on servers
  • Faster installation and startup of virtual machines/cloud images


Scope

  • Proposal owners:
    • Modify javapackages-tools package to automatically generate "java-headless" autorequires (simple change)
    • Identify and file bugs for affected packages (repoquery and bugzilla bug creation)
    • (optional) Mass-change spec files that have "Requires: java" to "Requires: java-headless"
  • Other developers:
  • Modify spec files to have "Requires: java-headless" instead of "Requires: java"
  • Release engineering:
    • mass rebuild is not necessary but it would simplify things
  • Policies and guidelines:
    • [Packaging:Java] needs to be modified to account for java-headless package existence

Upgrade/compatibility impact

Server systems with older Fedora versions that have "java-X.Y.Z-openjdk" package installed will possibly have unneeded packages installed after upgrade.

How To Test

Several Java packages in Fedora can be used to test java-headless change. After the change is implemented installation of following packages on top of minimal installation should not pull in pulseaudio and several X related packages:

  • ant
  • maven
  • wildfly
  • tomcat

Above packages should still work as designed even without "java-X.Y.Z-openjdk" package being installed.

User Experience

Smaller installation size and dependency chain when installing Java applications that do not require X system or audio capabilities.


Dependencies

No outside dependencies, Fedora has full control over all elements of this change.

Contingency Plan

  • Contingency mechanism:
    • Nothing needs to be done. If not all packages are converted, part of dependency chains might still pull in "java" package with full X and pulseaudio (i.e. no change from end-user perspective)
  • Contingency deadline:
    • None needed
  • Blocks release? No

Documentation

https://lists.fedoraproject.org/pipermail/java-devel/2013-October/004975.html

Release Notes