Re: [boost] proposal - modularize Boost build system

Subject: Re: [boost] proposal - modularize Boost build system
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2017-06-19 14:47:00

On 19.06.2017 10:32, Peter Dimov via Boost wrote:
> 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.

I have no idea why you are mentioning all this. How often do I need to
repeat that this proposal is about modularization, not about decoupling
the release process of individual Boost components ?

        Stefan

-- 
      ...ich hab' noch einen Koffer in Berlin...