Re: [boost] RFC: Separating Boost.Python from Boost

On May 31, 2015 12:14:57 AM EDT, Rene Rivera wrote:

On Fri, May 29, 2015 at 11:31 AM, Stefan Seefeld wrote:

...

as I have mentioned here before, I would very much like to continue the modularization effort, by fully separating the Boost.Python project from the rest of Boost. For avoidance of doubt: my intent is not to remove Boost.Python out of the Boost organization. Rather, I would like to separate the build and release processes.

As the author of the only Boost library that is both independently modular and at the same time part of Boost monolithic I'm not entirely opposed to the concept of making libraries modular. I do have reservations, as others have mentioned, with removing libraries from the monolithic release. I prefer the route of allowing the modular use of the libraries but keeping the "comprehensive" release (note my avoidance of monolithic).

[snip details] You've captured, in detail, the idea I tried to convey: modular is very likely a good idea, at least for many libraries, but a monolithic/comprehensive release remains necessary. ___ Rob (Sent from my portable computation engine)