Boost logo

Boost :

Subject: Re: [boost] Deprecation Policy
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2015-05-20 19:07:22

On 20/05/15 06:43 PM, Peter Dimov wrote:
> Stefan Seefeld wrote:
>>>> So, as I'm trying to get back into Boost.Python, I'm considering
>>>> decoupling that from the rest of Boost. I think this is an obvious
>>>> first candidate, notably because it's a substantial library (not
>>>> header-only) that few other Boost components depend on.
> ...
>> I very strongly believe that modularizing Boost will be beneficial
>> for everyone. I'm offering to do the first (experimental) steps with
>> Boost.Python in the hopes that this demonstrates the usefulness to
>> other library authors and maintainers who will then follow the same
>> path.
> I'm not sure I understand what you want to do. When you say
> "decoupling", what do you mean? Moving to a separate release schedule,
> or making Boost.Python not depend on other Boost libraries? What is
> your plan?

1) Allow Boost.Python to build stand-alone, i.e. against pre-installed
Boost dependencies.
2) Release Boost.Python independently from the rest of Boost.


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

Boost list run by bdawes at, gregod at, cpdaniel at, john at