From Fedora Project Wiki
< Changes
(→Scope) |
No edit summary |
||
| Line 1: | Line 1: | ||
<!-- 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 --> | ||
= | = Remove Guile Support From Toolchain = | ||
== Summary == | == Summary == | ||
GDB and | GDB and Make packages currently contain guile scripting support which allows users to implement | ||
(possibly new) functionality in these tools. This change request proposes to remove that support from | |||
the these tools, since both provide alternatives without the burden of additional dependencies. | |||
== Owner == | == Owner == | ||
| Line 46: | Line 48: | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
== Feedback == | <!-- == Feedback == --> | ||
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
While GDB supplies a "minimal" package which disables all non-essential features for use in | |||
the buildroot, Make has no equivalent, and is always compiled with Guile support. This | |||
requires that the buildroot contains Guile. This proposal will help shrink the buildroot. | |||
Furthermore, GDB already supports a much more widely tested and feature-rich Python interface, | |||
and maintainers would like to remove the maintenance burden imposed by supporting multiple | |||
scripting interfaces. | |||
<!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | <!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | ||
| Line 81: | Line 91: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: Update package spec files. | ||
<!-- What work do the feature owners 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 the feature owners 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?--> | ||
* Other developers: | * Other developers: Update Make/GDB scripting files if using Guile. | ||
<!-- 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?--> | ||
| Line 97: | Line 106: | ||
* Trademark approval: N/A (not needed for this Change) | * Trademark approval: N/A (not needed for this Change) | ||
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --> | <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --> | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
Users with GDB and/or Make Guile scripts will need to update and/or rewrite their scripts. | |||
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== How To Test == | == How To Test == | ||
GDB: There is nothing to test. If you are using Guile scripts, you should rewrite with Python. | |||
Make: Rebuild packages if it is unknown whether they contain Guile scripts; otherwise, there | |||
is nothing to test. | |||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | ||
| Line 121: | Line 130: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== User Experience == | == User Experience == | ||
| Line 136: | Line 143: | ||
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | ||
--> | --> | ||
Guile scripts that extend the functionality of GDB or Make will stop working when users upgrade | |||
these packages. GDB users are encouraged to use GDB's Python interface instead. Make users | |||
should either use shell scripting or migrate to CMake, Meson, or some other build tool. | |||
== Dependencies == | == Dependencies == | ||
| Line 146: | Line 157: | ||
<!-- 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: Revert changes and restore GDB/Make support for Guile. <!-- 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: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 165: | Line 176: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | ||
--> | --> | ||
Release notes should mention the removal of Guile support in GDB/Make and suggest alternatives. | |||
Revision as of 19:32, 8 December 2020
Remove Guile Support From Toolchain
Summary
GDB and Make packages currently contain guile scripting support which allows users to implement (possibly new) functionality in these tools. This change request proposes to remove that support from the these tools, since both provide alternatives without the burden of additional dependencies.
Owner
- Name: Keith Seitz
- Email: keiths@redhat.com
Current status
- Targeted release: Fedora 34
- Last updated: 2020-12-08
- 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
Benefit to Fedora
While GDB supplies a "minimal" package which disables all non-essential features for use in the buildroot, Make has no equivalent, and is always compiled with Guile support. This requires that the buildroot contains Guile. This proposal will help shrink the buildroot.
Furthermore, GDB already supports a much more widely tested and feature-rich Python interface, and maintainers would like to remove the maintenance burden imposed by supporting multiple scripting interfaces.
Scope
- Proposal owners: Update package spec files.
- Other developers: Update Make/GDB scripting files if using Guile.
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Users with GDB and/or Make Guile scripts will need to update and/or rewrite their scripts.
How To Test
GDB: There is nothing to test. If you are using Guile scripts, you should rewrite with Python.
Make: Rebuild packages if it is unknown whether they contain Guile scripts; otherwise, there is nothing to test.
User Experience
Guile scripts that extend the functionality of GDB or Make will stop working when users upgrade these packages. GDB users are encouraged to use GDB's Python interface instead. Make users should either use shell scripting or migrate to CMake, Meson, or some other build tool.
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: Revert changes and restore GDB/Make support for Guile.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)
Release Notes
Release notes should mention the removal of Guile support in GDB/Make and suggest alternatives.