From Fedora Project Wiki
< Features
No edit summary |
No edit summary |
||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name. This keeps all features in the same namespace --> | <!-- The actual name of your feature page should look something like: Features/Your_Feature_Name. This keeps all features in the same namespace --> | ||
= | = Guile2 = | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | ||
Update Guile to version 2.0. | Update GNU Guile to version 2.0.7 in Fedora 19. | ||
== Owner == | == Owner == | ||
| Line 19: | Line 19: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/19 | Fedora 19 ]] | * Targeted release: [[Releases/19 | Fedora 19 ]] | ||
* Last updated: 01-21 | * Last updated: 2013-01-21 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
== Detailed Description == | == Detailed Description == | ||
<!-- 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. --> | ||
Current guile package will be upgraded to 2.0.7. | |||
compat-guile18 package will provide additional time for the packages to be | compat-guile18 package will provide additional time for the packages to be | ||
ported to | ported to guile-2.0.7. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 39: | Line 36: | ||
== Scope == | == Scope == | ||
<!-- What work do the 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 the 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?--> | ||
For the packages listed in Dependencies section, there are two ways of | |||
proceeding after upgrading Guile: | |||
patched (if necessary) to use the renamed autotools macros. | |||
a) The packages will have to be patched to Require and BuildRequire the | |||
compat-guile18(-devel) package. Furthermore, they will have to be patched (if | |||
necessary) to use the renamed autotools macros. | |||
b) The packages will be ported to use the new API. | |||
Since b) is not trivial, a) would be the preferred way to proceed. The patches | |||
to spec files and autotools macros are easy to implement. | |||
Packages that are already built will not have to be rebuilt (there are no soname | |||
bumps in the compat package) and should function without any problems. Only new | |||
releases will have to be patched. | |||
== How To Test == | == How To Test == | ||
| Line 58: | Line 67: | ||
--> | --> | ||
guile-1.8.8 should be properly obsoleted by compat-guile18. | * guile-1.8.8 should be properly obsoleted by compat-guile18. | ||
guile-1.8.8 should be properly upgraded to guile-2.0. | * guile-1.8.8 should be properly upgraded to guile-2.0.7. | ||
* If both compat-guile18 and guile-2.0.7 are installed, there should be no conflicts. | |||
* All affected packages build and run without any problems. | |||
== User Experience == | == User Experience == | ||
| Line 74: | Line 85: | ||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | ||
TeXmacs | * TeXmacs | ||
aisleriot | * aisleriot | ||
autogen | * autogen | ||
coot | * coot | ||
denemo | * denemo | ||
drgeo | * drgeo | ||
freehoo | * freehoo | ||
freetalk | * freetalk | ||
g-wrap | * g-wrap | ||
* geda-gattrib | |||
geda-gattrib | * geda-gnetlist | ||
geda-gnetlist | * geda-gschem | ||
geda-gschem | * geda-gsymcheck | ||
geda-gsymcheck | * geda-utils | ||
geda-utils | * gnubik | ||
gnubik | * gnucash | ||
gnucash | * gnurobots | ||
gnurobots | * gnutls-guile | ||
gnutls-guile | * graphviz-guile | ||
graphviz-guile | * guile-cairo | ||
guile-cairo | * guile-devel | ||
guile-devel | * guile-lib | ||
guile-lib | * libctl | ||
libctl | * libgeda | ||
libgeda | * lilypond | ||
lilypond | * mdk | ||
mdk | * rumor | ||
rumor | * trackballs | ||
trackballs | * xbindkeys | ||
xbindkeys | |||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. 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 "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
With compat-guile18 available, there is no need to fall back. | |||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
* Information about Guile 2 can be found at http://www.gnu.org/software/guile/download.html#releases. | * Information about Guile 2 can be found at http://www.gnu.org/software/guile/download.html#releases. | ||
* Fedora tracking bug: https://bugzilla.redhat.com/show_bug.cgi?id=678238. | |||
== Release Notes == | == Release Notes == | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
GNU Guile was updated to 2.0.7. | |||
== Comments and Discussion == | == Comments and Discussion == | ||
| Line 122: | Line 133: | ||
[[Category: | [[Category:FeatureAcceptedF19]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Latest revision as of 13:31, 1 March 2013
Guile2
Summary
Update GNU Guile to version 2.0.7 in Fedora 19.
Owner
- Name: Jan Synacek
- Email: <jsynacek@redhat.com>
Current status
- Targeted release: Fedora 19
- Last updated: 2013-01-21
- Percentage of completion: 100%
Detailed Description
Current guile package will be upgraded to 2.0.7.
compat-guile18 package will provide additional time for the packages to be ported to guile-2.0.7.
Benefit to Fedora
New version of GNU Guile will be available. Further development will be based on this package instead of the old version.
Scope
For the packages listed in Dependencies section, there are two ways of proceeding after upgrading Guile:
a) The packages will have to be patched to Require and BuildRequire the compat-guile18(-devel) package. Furthermore, they will have to be patched (if necessary) to use the renamed autotools macros.
b) The packages will be ported to use the new API.
Since b) is not trivial, a) would be the preferred way to proceed. The patches to spec files and autotools macros are easy to implement.
Packages that are already built will not have to be rebuilt (there are no soname bumps in the compat package) and should function without any problems. Only new releases will have to be patched.
How To Test
- guile-1.8.8 should be properly obsoleted by compat-guile18.
- guile-1.8.8 should be properly upgraded to guile-2.0.7.
- If both compat-guile18 and guile-2.0.7 are installed, there should be no conflicts.
- All affected packages build and run without any problems.
User Experience
End Users:
- No visible changes to the end user.
Developers:
- New Guile functionality and API.
Packagers:
- Some rebuilds and small patches needed. See Scope and Dependencies sections.
Dependencies
- TeXmacs
- aisleriot
- autogen
- coot
- denemo
- drgeo
- freehoo
- freetalk
- g-wrap
- geda-gattrib
- geda-gnetlist
- geda-gschem
- geda-gsymcheck
- geda-utils
- gnubik
- gnucash
- gnurobots
- gnutls-guile
- graphviz-guile
- guile-cairo
- guile-devel
- guile-lib
- libctl
- libgeda
- lilypond
- mdk
- rumor
- trackballs
- xbindkeys
Contingency Plan
With compat-guile18 available, there is no need to fall back.
Documentation
- Information about Guile 2 can be found at http://www.gnu.org/software/guile/download.html#releases.
- Fedora tracking bug: https://bugzilla.redhat.com/show_bug.cgi?id=678238.
Release Notes
GNU Guile was updated to 2.0.7.