< Features
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
== 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.x. | Current guile package will be upgraded to 2.0.x. | ||
| Line 39: | Line 37: | ||
<!-- 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 | For the packages listed in Dependencies section, there are two ways of | ||
proceeding after upgrading Guile | proceeding after upgrading Guile: | ||
a) The packages will have to be patched to Require and BuildRequire the | a) The packages will have to be patched to Require and BuildRequire the | ||
| Line 50: | Line 48: | ||
to spec files and autotools macros are easy to implement. | 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 | |||
the compat package). | 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 == | ||
Revision as of 13:52, 21 January 2013
Feature Name Guile2
Summary
Update GNU Guile to version 2.0.x 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: 50%
Detailed Description
Current guile package will be upgraded to 2.0.x.
compat-guile18 package will provide additional time for the packages to be ported to guile-2.0.x.
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.x.
- If both compat-guile18 and guile-2.0.x 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
None necessary.
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
No need for a release notes entry.