19 Jun
2017
19 Jun
'17
2:32 p.m.
Stefan Seefeld wrote:
Packaging and releasing are orthogonal concepts.
Not really. Releasing separately from Boost means that you now have two Boost versions to communicate: the version of Boost.Python, and the version of the preinstalled Boost against which it was built (I built, f.ex. libboost-python-1.65.0-1.53.0 in my CentOS 7 case.) This consequently affects your downstream dependencies, which also have to include these two versions, in addition to their own. So when a library X depends on Boost.Python and it's compiled against Boost.Python 1.65.0-1.53.0, its version would now be X-1.17-1.65.0-1.53.0. This is not compatible with Y-2.1-1.63.0-1.53.0, even though both are built in the same CentOS 7 environment.