Wiki https://fedoraproject.org/wiki/Changes/F40Boost183 This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == This change brings Boost 1.83 to Fedora. This will mean Fedora ships with a recent upstream Boost release. == Owner == * Name: [[User:jwakely| Jonathan Wakely]] * Email: jwakely@xxxxxxxxxx * Name: [[User:ppalka| Patrick Palka]] * Email: ppalka@xxxxxxxxxx == Detailed Description == The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is absent from Boost, this entails rebuilding of all dependent packages. This also entails the change owner assisting maintainers of client packages in decoding cryptic boost-ese seen in output from g++. The equivalent changes for previous releases were [[Changes/F39Boost181]], [[Changes/F37Boost178]], [[Changes/F35Boost176]], [[Changes/F34Boost175]], [[Changes/F33Boost173]], [[Changes/F30Boost169|Fedora 30 Change]], [[Changes/F29Boost167|Fedora 29 Change]], [[Changes/F28Boost166|Fedora 28 Change]], [[Changes/F27Boost164|Fedora 27 Change]], [[Changes/F26Boost163|Fedora 26 Change]], [[Changes/F25Boost161|Fedora 25 Change]], [[Changes/F24Boost160|Fedora 24 Change]], [[Changes/F23Boost159|Fedora 23 Change]] and [[Changes/F22Boost158|Fedora 22 Change]]. == Benefit to Fedora == Fedora 40 includes Boost 1.83. Fedora will stay relevant, as far as Boost clients are concerned. Boost 1.83 and 1.82 do not bring any new components, but includes two new header-only libraries - * Compat: A repository of C++11 implementations of standard components added in later C++ standards, from Peter Dimov and contributors. * Mysql: A C++11 client for the MySQL database server, based on Boost.Asio, from Ruben Perez. Boost 1.83 also includes many fixes and enhancements to existing components, including major and potentially breaking changes to * Multi-index Containers: Serialization now uses std::size_t instead of unsigned long to save and load the size of a multi_index_container (unsigned long is smaller than std::size_t in LLP64 data models). multi_index_container serialization class version has been bumped from 3 to 4 to reflect this change. * Timer: Disable deprecated headers unless BOOST_TIMER_ENABLE_DEPRECATED is defined. Additionally the following breaking changes were introduced in Boost 1.82 and so also affect 1.83: * Atomic: Removed atomic<T>::storage() accessors and atomic<T>::storage_type types that were deprecated in Boost.Atomic 1.73. Users are recommended to use atomic<T>::value() and atomic<T>::value_type instead. * Geometry: The WKT output presentation of an empty polygon is now POLYGON() to make it consistent with other geometries * Math: Deprecated C++11 support. * Multiprecision: Deprecated C++11 support. * Process: Deprecated wait_for & wait_until in V1 - they will be removed in the future! == Scope == * Proposal owners: ** Build will be done with Boost.Build v2 (which is the upstream-sanctioned way of building Boost) ** Request a "f40-boost" [https://docs.pagure.org/releng/sop_adding_side_build_targets.html build system tag] ([http://lists.fedoraproject.org/pipermail/devel/2011-November/159908.html discussion]): <!-- N.B. next time use the side tag template: https://pagure.io/releng/issue/9419#comment-644377 --> ** Build boost into that tag (take a look at the [http://koji.fedoraproject.org/koji/buildinfo?buildID=606493 build #606493] for inspiration) ** Post a request for rebuilds to fedora-devel ** Work on rebuilding dependent packages in the tag. ** When most is done, re-tag all the packages to rawhide ** Watch fedora-devel and assist in rebuilding broken Boost clients (by fixing the client, or Boost). * Other developers: ** Those who depend on Boost DSOs will have to rebuild their packages. Feature owners will alleviate some of this work as indicated above, and will assist those whose packages fail to build in debugging them. * Release engineering: TODO <!-- [https://pagure.io/releng/issue/9421 #9421] --> (a check of an impact with Release Engineering is needed) * Policies and guidelines: ** Apart from scope, this is business as usual, so no new policies, no new guidelines. * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == * No manual configuration or data migration needed. * Some impact on other packages needing code changes to rebuild. Historically this hasn't been too much of a problem and could always be resolved before deadline. == How To Test == * No special hardware is needed. * Integration testing simply consists of installing Boost packages (`dnf install boost`) on Fedora and checking that it does not break other packages (see below for a way to obtain a list of boost clients). == User Experience == * Expected to remain largely the same. * Developers building third-party software on Fedora may need to rebuild against the new Boost packages, and may need to adjust their code if the new Boost release is not source-compatible. == Dependencies == Packages that must be rebuilt: <code>$ dnf repoquery -s --releasever=rawhide --whatrequires libboost\* --disablerepo=* --enablerepo=fedora | sort -u</code> All clients: <code>$ dnf repoquery --releasever=rawhide --archlist=src --whatrequires boost-devel --disablerepo='*' --enablerepo=fedora-source</code> == Contingency Plan == * Contingency mechanism: Worst case scenario is to abandon the update and simply ship F40 with Boost 1.81, which is already in rawhide. * Blocks release? No * Blocks product? None == Documentation == * https://www.boost.org/users/history/version_1_83_0.html (released on 11th August 2023) * https://www.boost.org/users/history/version_1_82_0.html (released on 14th April 2023) * https://www.boost.org/users/history/version_1_81_0.html (released on 14th December 2022) * https://www.boost.org/development/index.html == Release Notes == <!-- TODO --> -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-announce-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
