From Fedora Project Wiki

Boost 1.90 upgrade

Summary

This change brings Boost 1.90.0 to Fedora. This will mean Fedora ships with a recent upstream Boost release.

Owner


Current status

Detailed Description

The aim is to synchronize Fedora with the most recent Boost release. Fedora has not had a new Boost update since F40, so it is overdue. 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/F40Boost183, Changes/F39Boost181, Changes/F37Boost178, Changes/F35Boost176, Changes/F34Boost175, Changes/F33Boost173, Fedora 30 Change, Fedora 29 Change, Fedora 28 Change, Fedora 27 Change, Fedora 26 Change, Fedora 25 Change, Fedora 24 Change, Fedora 23 Change and Fedora 22 Change.


Feedback

Benefit to Fedora

Fedora 44 includes Boost 1.90.

Fedora will stay relevant, as far as Boost clients are concerned.

New libraries:

  • Charconv, Cobalt, Hash2, MQTT5, OpenMethod, Parser, Redis, Scope.

Updated libraries:

  • Most libraries no longer support C++03 and require at least C++11: Any, Asio, Atomic, Bind, Chrono, ContainerHash, Conversion, CRC, DLL, Filesystem, Format, Function, Graph (requires C++14), Heap, Iterator, LexicalCast, Lockfree, Log, MSM, Optional, Random, Ratio, SmartPtr, Stacktrace, System, Test, Thread, TypeIndex, TypeOf, Unordered, UUID, Variant.


Scope

  • Proposal owners:
    • Build will be done with Boost.Build v2 (which is the upstream-sanctioned way of building Boost)
    • Request a "f44-boost" build system tag (discussion): Using self-service side tag f44-build-side-125975
    • Build boost into that tag (take a look at the build #606493 for inspiration)
    • Post an announcement of starting 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.
  • Policies and guidelines:
    • No changes to policies or guidelines. This is business as usual.
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with the Fedora Strategy:
    • This proposal seems unlikely to increase the number of contributors to Fedora (but won't hurt either).

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 the deadline.

Early Testing (Optional)

Do you require 'QA Blueprint' support? No

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.
    • The boost-system subpackage is now empty and no libboost_system.so file is installed. Packages which link to libboost_system should drop it from their build, it is not needed.

Dependencies

Packages that must be rebuilt: $ dnf repoquery --sourcerpm --releasever=rawhide --whatrequires libboost\* --disablerepo=* --enablerepo=fedora | sort -u

All clients that consume Boost headers (these don't need to rebuilt if they don't depend on any libboost_*.so shared libraries): $ dnf repoquery --releasever=rawhide --archlist=src --whatrequires boost-devel --disablerepo='*' --enablerepo=fedora-source


Contingency Plan

  • Contingency mechanism: Worst case scenario is to abandon the update and simply ship F44 with Boost 1.83, which is already in rawhide.


  • Blocks release? No
  • Blocks product? None

Documentation

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/F44_Boost_1_90&oldid=761223"