Owner

Current status

Detailed Description

The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of all dependent packages. This has also always entailed yours truly assisting maintainers of client packages in decoding cryptic boost-ese seen in output from g++. Such care is to be expected this time around as well.

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.

Apart from scope, this is business as usual, so no policies, no guidelines.

Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

No impact on system upgrade.

No manual configuration or data migration needed.

Some impact on other packages. Historically this hasn't been too big 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.

Release Notes

(Incomplete) Boost has been upgraded to version 1.66. Apart from a number of bugfixes and improvements to existing libraries, this brings several new libraries compared to Fedora 27: Boost.PolyCollection, Boost.Stacktrace, Boost.Beast, Boost.CallableTraits, Boost.Mp11.