From Fedora Project Wiki

Fedora 14 Boost 1.44 Uplift


That feature brings version 1.44.0 of Boost to Fedora 14.


Current status

  • Targeted release: Fedora 14
  • Last updated: 2010-06-24
  • Percentage of completion: 0%

Detailed Description

That feature aims at synchronising the top of the Fedora tree with the current Boost upstream release. The current Fedora release is boost-1.41.0, folded into devel 2009-11-17.

As of Fedora 13, the canonical sources used for the package switched from the official Boost release (with BJam build) to an alternate repository (with CMake build, for boost-1.41.0). That alternate repository seems to be no longer actively maintained.

The challenge is therefore to go on packaging with CMake. If that fails, Fedora packaging will have to switch back to BJam build. In case it is successful, however, Fedora 14 should ship with Boost 1.44.

Some background:

  • Boost package in Fedora
  • Fedora 13 Boost-1.41 Feature
  • 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 had worked for over a year on a more standard way to build Boost, thanks to the CMake tool, namely Boost-CMake. However, the activity of that group has stalled since December 2009. Some members of the group would help any initiative, but nobody has taken the lead yet.

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.


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!


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.


Release Notes

  • Boost 1.40.0 Release Notes

  • Boost 1.41.0 Release Notes

Comments and Discussion