m (Fix category)
m (typo: java-headlesss)
|Line 4:||Line 4:|
== Summary ==
== 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-
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-instead of full java package when appropriate.
== Owner ==
== Owner ==
Revision as of 15:08, 15 November 2013
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-headless instead of full java package when appropriate.
- Name: Stanislav Ochotnicky
- Email: email@example.com
- Release notes owner:
- Targeted release: Fedora 21
- Last updated: 4-05-2015
- Tracker bug: <will be assigned by the Wrangler>
OpenJDK package in Fedora has been traditionally monolithic, pulling in a lot of dependencies including (but not limited to)
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 on java-devel are unaffected.
Benefit to Fedora
- Significantly smaller installation size on servers
- Faster installation and startup of virtual machines/cloud images
- Faster Java builds
- 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"
- (note) JavaSIG has several proven packages that could assist with this change
- Release engineering:
- mass rebuild is not necessary but it would simplify things
- Policies and guidelines:
Systems with older Fedora versions that have "java-X.Y.Z-openjdk" package installed will possibly have unneeded packages installed after upgrade. This does not negatively impact the users except wasted storage space.
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:
Above packages should still work as designed even without "java-X.Y.Z-openjdk" package being installed. Failures would be visible immediately after trying to run an application
Exampole steps to test:
- Install minimal installation of Fedora
- Install Java application for testing
- Verify only java-X.Y.Z-openjdk-headless package is installed and not full java-X.Y.Z-openjdk
- Verify that tested Java application works (differs from application to application)
Smaller installation size and dependency chain when installing Java applications that do not require X system or audio capabilities.
No outside dependencies, Fedora has full control over all elements of this change.
- 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