From Fedora Project Wiki
(Created page with '{{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 rea...')
 
 
(20 intermediate revisions by 2 users not shown)
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.
<!-- 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.  -->
  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 -->
<!-- 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 15 Boost 1.46 Uplift =


== 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. -->
This feature brings Boost 1.46.0 to Fedora 15.


== Owner ==
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:Denisarnaud| Denis Arnaud]]
* Name: [[User:FASAcountName| Your Name]]
* Email: denis.arnaud_fedora@m4x.org


<!-- 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-->
== Current status ==
* Email: <your email address so we can contact you, invite you to meetings, etc.>
* Targeted release: [[Releases/15/Schedule |Fedora 15]] (and its [[Releases/15/FeatureList |Feature List]])
* Last updated: 2011-04-22
* Percentage of completion: 100%
** [https://admin.fedoraproject.org/updates/boost-1.46.1-1.fc15 The final version of Boost-1.46.1 has been successfully built] and submitted to F15 testing (on Mar. 13th, 2011)
** All the packages depending on Boost-1.46.0-beta1 had been rebuilt
** Since Boost-1.46.1 [https://github.com/boost-lib/boost-cmake/compare/pristine-1.46.0-beta_1...pristine-1.46.1 only brings (small) bug fixes and documentation updates], there should be no risk of ABI incompatibility


== Current status ==
== Detailed Description ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
That feature aims at synchronising the top of the Fedora tree with the current Boost upstream release. The current Fedora release is boost-1.44.0, folded into devel August 2010.
* Last updated: (DATE)
 
* Percentage of completion: XX%
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.
boost-1.41.0 has been delivered from that (now deprecated) Boost-CMake repository (hosted on [http://gitorious.org/~zeuner/boost/zeuners-boost-cmake 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 [https://github.com/denisarnaud/boost-cmake GitHub] (and cloned on [http://gitorious.org/~denisarnaud/boost/denisarnauds-cmake Gitorious]). That repository relies on the [http://ryppl.github.com Ryppl project], created and maintained by two talented Boost developers, namely [https://github.com/ericniebler Eric Niebler] and [https://github.com/dabrahams Dave Abrahams].
 
The objective is now to keep delivering the latest stable Boost release for each new Fedora and RedHat releases.
 
Some background:
 
* [https://admin.fedoraproject.org/pkgdb/acls/name/boost Boost package in Fedora]
* [http://koji.fedoraproject.org/koji/packageinfo?packageID=1074 Boost build status in Koji]
* [[Features/F14Boost144 |Fedora 14 Boost-1.44 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_45_0/more/getting_started/unix-variants.html#get-bjam BJam].
 
Technical details are available in a [https://bugzilla.redhat.com/show_bug.cgi?id=656410 Bugzilla-filed (#656410)] enhancement request.


<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->


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


== Benefit to Fedora ==
== 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.
* With every new release of Boost come new components and libraries. For instance, Boost 1.46 brings [http://www.boost.org/libs/icl/index.html ICL], and Boost 1.45 had already brought [http://www.boost.org/doc/libs/1_45_0/libs/msm/index.html MSM] and [http://www.boost.org/doc/libs/1_45_0/libs/polygon/index.html Polygon].
* Moreover, the existing components and libraries are enhanced with new features and bug fixes. For instance, the [http://www.boost.org/doc/libs/1_45_0/?view=category_Math Boost.Math components] have now become better than the [http://www.gnu.org/software/gsl/ GSL] for support to [http://www.boost.org/doc/libs/1_45_0/libs/math/doc/sf_and_dist/html/index.html statistical analysis].


== 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?-->
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 ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.  
* 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 15 and checking that it does not break any other package dependency.
* Expected results: all the packages depending on Boost (for instance, hugin, gnash, pingus, kdeedu or k3d) should work properly on Fedora 15.


Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
== User Experience ==
Expected to remain largely the same.


A good "how to test" should answer these four questions:
== Dependencies ==
 
There are a large number of dependencies for the boost package in fedora. Here is a non-exhaustive list.
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->


== User Experience ==
<pre>
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
aqsis
asc
avogadro
barry
bastet
bmpx
CGAL
chess
conexus
dchroot
deluge
easystroke
enblend
esperanza
fuse-encfs
fusecommon
1:fife
glob2
glom
gnash
gnote
gnuradio
gpsdrive
HippoDraw
hugin
libpst-python
LuxRender
lyx
k3d
kdeedu
linkage
mapnik
Miro
mkvtoolnix
openvrml
pingus
player
pokerth
pyexiv2
pymilia
python-gnash
python-polybori
python-tag
qbittorent
qpidc
QuantLib
rb_libtorrent
rcsserver3d
rcsslogplayer
rcssserver
referencer
rmol
schroot
simspark
soci
source-highlight
spring
torium
twinkle
urge
usrp
vegastrike
vigra-python
wesnoth
widelands
wp_tray
xmms2
xsd
</pre>


== Dependencies ==
Rebuilt for f15, +24 hours
<!-- 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)? -->
<pre>
asc
chess
deluge
fuse-encfs
gnash
mapnik
pingus
python-tag
referencer
source-highlight
</pre>


== 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. -->
Non-completion will result in the F14 boost version, 1.44.0, being used in F15.


== 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. -->
* Boost: http://www.boost.org/doc/libs/1_46_0
*
* Boost-CMake: http://github.com/boost-lib/boost-cmake ([https://svn.boost.org/trac/boost/wiki/CMake the previous wiki] is now outdated)


== 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/ -->
* Boost 1.46.0 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. -->
 
*
http://www.boost.org/users/news/version_1_46_0
 
* Boost 1.45.0 Release Notes
 
http://www.boost.org/users/news/version_1_45_0
 
* Boost 1.44.0 Release Notes
 
http://www.boost.org/users/news/version_1_44_0


== Comments and Discussion ==
== 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/F15Boost146]]
 
* BZ: https://bugzilla.redhat.com/show_bug.cgi?id=656410
** for Fedora 14 and Boost-1.44: https://bugzilla.redhat.com/show_bug.cgi?id=607615
** for Fedora 13 and Boost-1.41: https://bugzilla.redhat.com/show_bug.cgi?id=529563
* Status
** Boost-1.46.0-0.4, corresponding to the final 1.46.0 version of Boost, has been successfully built:
*** Rawhide: http://koji.fedoraproject.org/koji/taskinfo?taskID=2864627 => http://kojipkgs.fedoraproject.org/packages/boost/1.46.0/0.4.fc16/
*** [https://admin.fedoraproject.org/updates/boost-1.46.0-0.4.fc15 F15]: http://koji.fedoraproject.org/koji/taskinfo?taskID=2869175 => http://kojipkgs.fedoraproject.org/packages/boost/1.46.0/0.4.fc15/


[[Category:FeaturePageIncomplete]]
[[Category:FeatureAcceptedF15]]
<!-- 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 16:53, 22 April 2011


Fedora 15 Boost 1.46 Uplift

Summary

This feature brings Boost 1.46.0 to Fedora 15.

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.44.0, folded into devel August 2010.

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. 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, created and maintained by two talented Boost developers, namely Eric Niebler and Dave Abrahams.

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

Some background:

Technical details are available in a Bugzilla-filed (#656410) enhancement request.


Benefit to Fedora

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

  • With every new release of Boost come new components and libraries. For instance, Boost 1.46 brings ICL, and Boost 1.45 had already brought MSM and Polygon.
  • Moreover, the existing components and libraries are enhanced with new features and bug fixes. For instance, the Boost.Math components have now become better than the GSL for support to statistical analysis.

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 15 and checking that it does not break any other package dependency.
  • Expected results: all the packages depending on Boost (for instance, hugin, gnash, pingus, kdeedu or k3d) should work properly on Fedora 15.

User Experience

Expected to remain largely the same.

Dependencies

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

aqsis
asc
avogadro
barry
bastet
bmpx
CGAL
chess
conexus
dchroot
deluge
easystroke
enblend
esperanza
fuse-encfs
fusecommon
1:fife
glob2
glom
gnash
gnote
gnuradio
gpsdrive
HippoDraw
hugin
libpst-python
LuxRender
lyx
k3d
kdeedu
linkage
mapnik
Miro
mkvtoolnix
openvrml
pingus
player
pokerth
pyexiv2
pymilia
python-gnash
python-polybori
python-tag
qbittorent
qpidc
QuantLib
rb_libtorrent
rcsserver3d
rcsslogplayer
rcssserver
referencer
rmol
schroot
simspark
soci
source-highlight
spring
torium
twinkle
urge
usrp
vegastrike
vigra-python
wesnoth
widelands
wp_tray
xmms2
xsd

Rebuilt for f15, +24 hours 

asc
chess
deluge
fuse-encfs
gnash
mapnik
pingus
python-tag
referencer
source-highlight

Contingency Plan

Non-completion will result in the F14 boost version, 1.44.0, being used in F15.

Documentation

Release Notes

  • Boost 1.46.0 Release Notes

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

  • Boost 1.45.0 Release Notes

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

  • Boost 1.44.0 Release Notes

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

Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/F15Boost146&oldid=233213"