Subject: Re: [boost] RFC: Separating Boost.Python from Boost
From: Nevin Liber (nevin_at_[hidden])
Date: 2015-05-29 15:35:48
On 29 May 2015 at 13:32, Stefan Seefeld <stefan_at_[hidden]> wrote:
> On 29/05/15 02:26 PM, Nevin Liber wrote:
> > On 29 May 2015 at 13:12, Stefan Seefeld <stefan_at_[hidden]> wrote:
> >> Again, no code changes are involved. Right now Boost.Python is built as
> >> part of a Boost build, and likewise is released as part of a Boost
> >> release. All I'm suggesting is to build and release Boost.Python
> >> stand-alone, against an external Boost installation.
> > Does that mean Boost.Python would no longer be part of a Boost release?
> That would be the goal, yes. (Boost.Python doesn't have any dependencies
> on recent Boost additions, so I expect it to be very stable with respect
> to ongoing development in the rest of the Boost code.)
I am strongly against breaking up the Boost release.
I also think such a fundamental change has to go through the Steering
-- Nevin ":-)" Liber <mailto:nevin_at_[hidden]> (847) 691-1404
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk