From Fedora Project Wiki
No edit summary
No edit summary
Line 33: Line 33:
* [[Features/F13Boost141 |Fedora 13 Boost-1.41 Feature]]
* [[Features/F13Boost141 |Fedora 13 Boost-1.41 Feature]]
* [http://www.boost.org Boost] ships with an ad-hoc build system named [http://www.boost.org/doc/libs/1_47_0/more/getting_started/unix-variants.html#get-bjam BJam].
* [http://www.boost.org Boost] ships with an ad-hoc build system named [http://www.boost.org/doc/libs/1_47_0/more/getting_started/unix-variants.html#get-bjam BJam].
Technical details are available in a [https://bugzilla.redhat.com/show_bug.cgi?id=754865 Bugzilla-filed (#754865)] enhancement request.


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 44: Line 42:
* Assess whether cmake upstream is ready, possibly help patch the holes
* Assess whether cmake upstream is ready, possibly help patch the holes
* Do the initial packaging work (possibly on a branch), add sub-packages for new runtime components
* Do the initial packaging work (possibly on a branch), add sub-packages for new runtime components
* Request a build system tag ([http://lists.fedoraproject.org/pipermail/devel/2011-November/159908.html discussion])
* Request a "boost" build system tag ([http://lists.fedoraproject.org/pipermail/devel/2011-November/159908.html discussion])
* Build boost into that tag
* Build boost into that tag
* Post a request for rebuilds to fedora-devel
* Post a request for rebuilds to fedora-devel
* Work on rebuilding dependent packages in the tag, fixing any bugs it either the dependent package, or Boost
* Work on rebuilding dependent packages in the tag, fixing any bugs it either the dependent package, or Boost
* When most is done, "merge" the tag
* When most is done, re-tag all the packages to rawhide


== How To Test ==
== How To Test ==
Line 59: Line 57:


== Dependencies ==
== Dependencies ==
There are a large number of dependencies for the boost package in Fedora. Following is a non-exhaustive list, collected from the first Rawhide report:
There are a large number of dependencies for the boost package in Fedora. The list of packages that really _need_ rebuilding can be obtained as follows:
{{{
$ repoquery -s --whatrequires libboost\* | sort -u
}}}


<pre>
Those are libraries that won't even start after boost update, because each Boost update implies a soname bump.  Currently this returns 104 packages.
airrac
airsched
akonadi
aqsis
aqsis-core
aqsis-libs
asc
avogadro
avogadro-libs
barry
bastet
cclive
cegui-python
CGAL
collada-dom
compiz
compiz-fusion-extras
compiz-fusion-unsupported
compiz-gtk
compiz-kde
compiz-plugins-main
easystroke
ekiga
ember
esteid-browser-plugin
fatrat
fawkes-plugin-player
fife
flush
fusecompress
fuse-encfs
gearmand
glob2
glom
glom-libs
gnash
gnash-cygnal
gnash-klash
gnuradio
gpsdrive
guitarix
HippoDraw-python
hugin
hugin-base
iwhd
k3d
kalzium
kalzium-libs
kig
libcompizconfig
libmapi
libmongodb
libopenvrml
libopenvrml-gl
libpst-python
LuxRender
LuxRender-core
LuxRender-devel
LuxRender-lib
lyx
mapnik
mapnik-python
mapnik-utils
mbox2eml
minion
mkvtoolnix
mkvtoolnix-gui
mmseq
mongodb
mongodb-server
mygui
mygui-demos
mygui-devel
mygui-tools
nss-gui
ogre
ogre-samples
ompl
OpenImageIO
openvrml-java
openvrml-javascript
openvrml-nodes
openvrml-xembed
pdns
perl-qpid
pingus
player
plee-the-bear
pokerth
pyactivemq
pyexiv2
pymilia
python-gnash
python-polybori
python-tag
python-visual
qbittorrent
qbittorrent-nox
qpid-cpp-client
qpid-cpp-client-devel
qpid-cpp-client-rdma
qpid-cpp-client-ssl
qpid-cpp-server
qpid-cpp-server-cluster
qpid-cpp-server-rdma
qpid-cpp-server-ssl
qpid-cpp-server-store
qpid-cpp-server-xml
qpid-qmf
QuantLib-test
rb_libtorrent
rb_libtorrent-examples
rb_libtorrent-python
rcsslogplayer
rcssmonitor
rcssserver
rmol
ruby-qpid-qmf
schroot
simfqt
simspark
source-highlight
spring
springlobby
stdair
swift
tncfhh-examples
tncfhh-libs
travelccm
twinkle
undertaker
vegastrike
vigra-python
votca-csg
votca-csg-libs
votca-tools
wesnoth
wesnoth-server
wesnoth-tools
wlmproxy
xsd
zarafa-server
</pre>


== Contingency Plan ==
== Contingency Plan ==

Revision as of 16:29, 28 May 2012

Fedora 18 Boost 1.50 Uplift

Summary

This feature brings Boost 1.50.0 to Fedora 18.

Owner

Current status

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.48.0.

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 has been deprecated and may be deleted any time soon (as of November 2011). boost-1.41.0 has been delivered from that (now deprecated) Boost-CMake repository (hosted on Gitorious), where the code base had slightly diverged from upstream.

From Fedora 14, boost-1.44.0 has been rebased on upstream, with a mere patch implementing CMake support. Moreover, there is a new Git repository reflecting those changes, hosted on GitHub (and cloned on Gitorious). That repository relies on the Ryppl project (in particular, on the Boost Subversion replicated repository), created and maintained by two Boost developers, namely Eric Niebler and Dave Abrahams.

The objective is now to keep delivering the latest stable Boost release for each new Fedora release.

Some background:

Benefit to Fedora

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

Scope

The following needs to be done:

  • Assess whether cmake upstream is ready, possibly help patch the holes
  • Do the initial packaging work (possibly on a branch), add sub-packages for new runtime components
  • Request a "boost" build system tag (discussion)
  • Build boost into that tag
  • Post a request for rebuilds to fedora-devel
  • Work on rebuilding dependent packages in the tag, fixing any bugs it either the dependent package, or Boost
  • When most is done, re-tag all the packages to rawhide

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.
  • Integration testing simply consists of installing Boost packages on Fedora 18 and checking that it does not break other packages.

User Experience

Expected to remain largely the same.

Dependencies

There are a large number of dependencies for the boost package in Fedora. The list of packages that really _need_ rebuilding can be obtained as follows:

sort -u


Those are libraries that won't even start after boost update, because each Boost update implies a soname bump. Currently this returns 104 packages.

Contingency Plan

Since we will build in a separate tag, if anything goes wildly wrong, the natural result would be abandoning that tag and shipping Fedora 18 with boost-1.48.

Documentation

Release Notes

  • Boost 1.50.0 Release Notes

http://www.boost.org/users/news/version_1_50_0

  • Boost 1.49.0 Release Notes

http://www.boost.org/users/news/version_1_49_0

Comments and Discussion