(Initial change proposal) |
m (Add trackers) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 19: | Line 19: | ||
<!-- 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 --> | ||
= | = Move Gold Into A SubpackageOf Binutils <!-- The name of your change proposal --> = | ||
== Summary == | == Summary == | ||
| Line 56: | Line 56: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1686976 #1686976] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/309 #309] | |||
== Detailed Description == | == Detailed Description == | ||
| Line 176: | Line 177: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: | * Contingency mechanism: Restore GOLD to the main binutils package. This can be done by anyone familair with spec files, although ideally it would be done by the binutils packahe maintainer (ie me). <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: | * Contingency deadline: F31 release. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? | * Blocks product? No <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
== Documentation == | == Documentation == | ||
| Line 198: | Line 197: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF31]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 19:28, 8 March 2019
Move Gold Into A SubpackageOf Binutils
Summary
Move the GOLD linker from the main binutils package into its own sub-package.
Owner
- Name: Nick Clifton [1]
- Email: nickc@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 31
- Last updated: 2019-03-08
- Tracker bug: #1686976
- Release notes tracker: #309
Detailed Description
The GOLD linker is currently part of the binutils package. Unfortunately it seems that Google have decided not to continue development of the linker, and so it is possible that it may start to bit-rot. The linker is still being maintained by the upstream GNU Binutils project, but new development is not happening. Thus as a precautionary measure I would like to move GOLD into its own sub-package of the binutils, in case in the future we decide that it should be deprecated.
Benefit to Fedora
In the short term none. Although also in the short term the change should have no effect on Fedora. In the long term moving the gold linker into its own package means that it could then be removed from Fedora, should it turn out to be unmaintainable.
Scope
- Proposal owners:
Create a sub-package of the binutils package containing just the gold linker.
- Other developers:
Packages that use the gold linker should add a requirement on the new sub-package.
- Release engineering: https://pagure.io/releng/issue/8130 (a check of an impact with Release Engineering is needed)
A mass rebuild would be useful as it will help to identify packages that need to update their requirements.
- Policies and guidelines: The packaging guidelines should be updated to indicate that any package that uses the gold linker should have a requirement on the new sub-package.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
In theory there should be no impact when upgrading. As long as packages that need a linker have a dependency upon the binutils package, the new gold sub-package should be included as well.
How To Test
No special hardware is needed, but a environment capable of building packages is desirable. First install the binutils package (if not already installed) and make sure that both ld.bfd and ld.gold are in the search path. Then try uninstalling the binutils-gold sub-package. This should remove ld.gold. Try reinstalling it, which should restore ld.gold.
User Experience
Ideally users should not notice any difference in their experience with Fedora.
Dependencies
None.
Contingency Plan
- Contingency mechanism: Restore GOLD to the main binutils package. This can be done by anyone familair with spec files, although ideally it would be done by the binutils packahe maintainer (ie me).
- Contingency deadline: F31 release.
- Blocks release? No
- Blocks product? No
Documentation
None written yet.