Latest revision as of 00:59, 28 July 2010

Fedora 13 Boost 1.41 Uplift

Summary

That feature brings version 1.41.0 of Boost to Fedora 13, together with Boost.MPI. As a side effect, Boost will be built with CMake (instead of BJam).

Owner

Name: Denis Arnaud
Email: denis.arnaud_fedora@m4x.org

Current status

Targeted release: Fedora 13
Last updated: 2010-02-03
Percentage of completion: 100%

Detailed Description

Sync top of the Fedora tree to the current upstream release. The current Fedora release is boost-1.39.0, folded into devel 2009-05-07. This upgrade is in keeping with vaguely bi-annual, opportunistic syncing with upstream sources.

In addition, this update changes the canonical sources used for the package from the official Boost release to an alternate repository.

Some background:

Boost ships with an ad-hoc build system named BJam. The Boost development community is exploring alternate build and source code control approaches, including the use of more standard build and release management tools like git and CMake. Which, frankly, the Fedora boost maintainers wish to support. Fortunately for us, a team of developers has worked for over a year on a more standard way to build Boost, thanks to the CMake tool, namely Boost-CMake.

That new way to build Boost allows (at least) two enhancements, when compared to the current build system:

Deliver some more libraries, such as Boost.MPI
Keep more easily synchronized with the latest Boost versions (Fedora 13 should ship with Boost 1.41.0).

Technical details are available in a Bugzilla-filed enhancement request.

Benefit to Fedora

Syncing with upstream keeps Fedora current. This is part of regular package maintenance.

Scope

Upstream sources for Boost releases are evaluated, along with alternate repositories. One is selected, packaged according to Fedora package conventions and cognizant of existing package practices, tested, evaluated, and then built in Koji. This is then pushed to fedora devel. Dependencies are rebuilt. The unicorns are once again happy, and can go back to drinking champagne and complaining about slow build times.

How To Test

No special hardware is needed.
Testing of the Boost packages themselves requires the host system to have the boost-test package installed. Testing can then be enabled at package build time by passing --with tests. Note that that testing phase should be done only once per type of architecture and distribution version.
Once the Boost packages have been built and checked according to the previous step, testing simply consists in installing them on Fedora 13 and checking that it does not break any other package dependency.
Expected results: all the packages depending on Boost (for instance, gnash, pingus, kdeedu or k3d) should work properly on Fedora 13.

Note: for more adventurous developers, the new Boost packages can also be built and installed on other versions of Fedora (beginning with Fedora 12), enabling the soname patch within the specification file according to the Fedora version (for instance, the soname should be 5 on F12 and 4 on F11). But that testing is not required for that feature to be completed: it is just extra sugar.

User Experience

Expected to remain largely the same. New users of boost-mpi, welcome!

Dependencies

There are a large number of dependencies for the boost package in fedora. Here is a non-exhaustive list.

openvrml pingus hugin conexus player mapnik aqsis qpidc deluge rcsslogplayer Miro asc glob2 vegastrike gnash chess pyexiv2 k3d kdeedu python-tag linkage barry rcssserver QuantLib wesnoth mkvtoolnix rb_libtorrent bmpx xmms2 wp_tray fuse-encfs referencer source-highlight HippoDraw rcsserver3d

Contingency Plan

Non-completion will result in the F12 boost version, 1.39.0, being used in F13.

Documentation

Boost: http://www.boost.org/doc/libs/1_41_0
Boost-CMake: https://svn.boost.org/trac/boost/wiki/CMake

Release Notes

Boost 1.40.0 Release Notes

http://www.boost.org/users/history/version_1_40_0

Boost 1.41.0 Release Notes

http://www.boost.org/users/history/version_1_41_0

Comments and Discussion

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
-{{admon/important | Set a Page Watch| Make sure you click ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
-{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
 <!-- All fields on this form are required to be accepted by FESCo.
   We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
@@ Line 11: / Line 4: @@
 <!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
-= Feature Name <!-- The name of your feature --> =
+= Fedora 13 Boost 1.41 Uplift =
 == 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. -->
+That feature brings version 1.41.0 of Boost to Fedora 13, together with Boost.MPI. As a side effect, Boost will be built with CMake (instead of BJam).
 == Owner ==
-<!--This should link to your home wiki page so we know who you are-->
 * Name: [[User:Denisarnaud| Denis Arnaud]]
-<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
 * Email: denis.arnaud_fedora@m4x.org
 == Current status ==
-* Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]]
+* Targeted release: [[Releases/13 | Fedora 13 ]]
-* Last updated: (DATE)
+* Last updated: 2010-02-03
-* Percentage of completion: XX%
+* Percentage of completion: 100%
+== Detailed Description ==
+Sync top of the Fedora tree to the current upstream release. The current Fedora release is boost-1.39.0, folded into devel 2009-05-07. This upgrade is in keeping with vaguely bi-annual, opportunistic syncing with upstream sources.
+In addition, this update changes the canonical sources used for the package from the official Boost release to an alternate repository.
+Some background:
-<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
+[http://www.boost.org Boost] ships with an ad-hoc build system named [http://www.boost.org/doc/libs/1_41_0/more/getting_started/unix-variants.html#get-bjam BJam]. The Boost development community is exploring alternate build and source code control approaches, including the use of more standard build and release management tools like git and CMake. Which, frankly, the Fedora boost maintainers wish to support. Fortunately for us, a team of developers has worked for over a year on a more standard way to build Boost, thanks to the [http://www.cmake.org CMake tool], namely [https://svn.boost.org/trac/boost/wiki/CMake Boost-CMake].
-== Detailed Description ==
+That new way to build Boost allows (at least) two enhancements, when compared to the current build system:
-<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+* Deliver some more libraries, such as Boost.MPI
+* Keep more easily synchronized with the latest Boost versions (Fedora 13 should ship with Boost 1.41.0).
+Technical details are available in a [https://bugzilla.redhat.com/show_bug.cgi?id=529563 Bugzilla-filed] enhancement request.
 == Benefit to Fedora ==
 <!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
+Syncing with upstream keeps Fedora current. This is part of regular package maintenance.
 == 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?-->
+Upstream sources for Boost releases are evaluated, along with alternate repositories. One is selected, packaged according to Fedora package conventions and cognizant of existing package practices, tested, evaluated, and then built in Koji. This is then pushed to fedora devel. Dependencies are rebuilt. The unicorns are once again happy, and can go back to drinking champagne and complaining about slow build times.
 == How To Test ==
@@ Line 53: / Line 56: @@
 . What are the expected results of those actions?
 -->
+* No special hardware is needed.
+* Testing of the Boost packages themselves requires the host system to have the boost-test package installed. Testing can then be enabled at package build time by passing <tt>--with tests</tt>. Note that that testing phase should be done only once per type of architecture and distribution version.
+* Once the Boost packages have been built and checked according to the previous step, testing simply consists in installing them on Fedora 13 and checking that it does not break any other package dependency.
+* Expected results: all the packages depending on Boost (for instance, gnash, pingus, kdeedu or k3d) should work properly on Fedora 13.
+Note: for more adventurous developers, the new Boost packages can also be built and installed on other versions of Fedora (beginning with Fedora 12), enabling the soname patch within the specification file according to the Fedora version (for instance, the soname should be 5 on F12 and 4 on F11). But that testing is not required for that feature to be completed: it is just extra sugar.
 == User Experience ==
 <!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+Expected to remain largely the same. New users of boost-mpi, welcome!
 == 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)? -->
+There are a large number of dependencies for the boost package in fedora. Here is a non-exhaustive list.
+openvrml
+pingus
+hugin
+conexus
+player
+mapnik
+aqsis
+qpidc
+deluge
+rcsslogplayer
+Miro
+asc
+glob2
+vegastrike
+gnash
+chess
+pyexiv2
+k3d
+kdeedu
+python-tag
+linkage
+barry
+rcssserver
+QuantLib
+wesnoth
+mkvtoolnix
+rb_libtorrent
+bmpx
+xmms2
+wp_tray
+fuse-encfs
+referencer
+source-highlight
+HippoDraw
+rcsserver3d
 == 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.  -->
+Non-completion will result in the F12 boost version, 1.39.0, being used in F13.
 == 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. -->
-*
+* Boost: http://www.boost.org/doc/libs/1_41_0
+* Boost-CMake: https://svn.boost.org/trac/boost/wiki/CMake
 == 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. -->
-*
+* Boost 1.40.0 Release Notes
+http://www.boost.org/users/history/version_1_40_0
+* Boost 1.41.0 Release Notes
+http://www.boost.org/users/history/version_1_41_0
 == Comments and Discussion ==
-* See [[Talk:Features/YourFeatureName]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
+* See [[Talk:Features/F13Boost141]]
+* BZ: https://bugzilla.redhat.com/show_bug.cgi?id=529563
-[[Category:FeaturePageIncomplete]]
+[[Category:FeatureAcceptedF13]]
 <!-- When your feature page is completed and ready for review -->
 <!-- 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-->
 <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Search

Features/F13Boost141: Difference between revisions