New library: Boost.Contract
The Python-related shared libraries now carry the full Python version,
eg _python27.so and _python37.so
Drop patches:
deleted: boost-1.66.0-address-model.patch
deleted: boost-1.66.0-compute.patch
deleted: boost-1.66.0-numpy3.patch
deleted: boost-1.66.0-python37.patch
deleted: boost-1.66.0-spirit-abs-overflow.patch
The Fedora OpenMPI and MPICH Flatpaks pose considerable challenges for
rebuilding to use in Flaptaks with prefix=/app - in particular because
of their use of environment-modules. An analysis of all graphical
applications in Fedora that we might want to create Flatpak containers
of shows no apps that use the OpenMPI and MPICH subpackages of boost,
though many other boost packages are used. So simply disabling openmpi
and mpich for Flatpak rebuilds is the simplest approach.
The %{python2_version} and %{python3_version} macros are pre-defined, so
we don't need to use ver.py to find the versions.
Use shell variable for Python 3 ABI flags instead of global macro. This
avoids errors when creating SRPMs or running rpmlint, because by
delaying the command until the %build stage we can rely on python3-devel
being installed.
Rename all subpackages using python2 from boost-xxx to boost-xxx2.
Split new subpackage boost-python2-devel out of boost-devel.
Split new subpackage boost-openmpi-python2-devel out of boost-openmpi-devel.
Split new subpackage boost-mpich-python2-devel out of boost-mpich-devel.
Enable conditional build for python2 packages.
The Group tag is not used by RPM.
In F28 the ldconfig %post and %postun scriptlets are done automatically
and so don't need to be explicit in the spec file.
This should hopefully fix linking with boost_context, which currently
fails on ppc64le with:
/usr/lib/gcc/ppc64le-redhat-linux/7/../../../../lib64/libboost_context.so:
undefined reference to `std::__once_functor@GLIBCXX_3.4.11'
