Re: Should boost package install boost-python2 / boost-python3 / both or none?
On 19/04/18 19:07 +0200, Miro Hrončok wrote:
I was recently surprised that `dnf install boost` brings in python2.
It is like that because boost brings in bost-python and that is
python2 ATM. I've reported it as a bug, because it bugs me :)
https://bugzilla.redhat.com/show_bug.cgi?id=1569483
However Jonathan Wakely (the boost maintainer) says this needs broader
audience.
So I'm asking here on devel:
Should the 'boost' metapackage install boost-python at all? If so,
what versions?
I think my preference would be to simply remove boost-python and
boost-numpy from the 'boost' package, and remove their headers and
shared library symlinks from the boost-devel package.
This would make the Boost.Python packaging consistent for python2 and
python3: you'd always need to explicitly choose which you want.
This will mean if you want to install Boost.Python you won't be able
to just use 'dnf install boost' you'll need to also install
boost-python2 or boost-python3 explicitly.
If you want to compile code using Boost.Python it won't be enough to
install boost-devel, you'll need to choose either boost-python2-devel
or boost-python3-devel.
The alternative would be to switch the "default" to be the python3
packages (and split some things out into new packages, e.g. currently
boost-mpich-devel installs %{_libdir}/mpich/lib/libboost_mpi_python.so
but this should really be in a separate boost-mpich-python2-devel
package).