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

On 29 May 2015, at 19:32, Stefan Seefeld wrote:

...

On 29/05/15 02:26 PM, Nevin Liber wrote:

...

On 29 May 2015 at 13:12, Stefan Seefeld 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.)

Stefan

As a corporate user of Boost and Boost.python on the face of it this a bad change for me. Right now Boost is one entity so from a legal and various bureaucratic points of view I can bring boost through the door in one fell swoop (I then apply another quality filter before it a particular library is used in anger). Multiple versions has the potential for headaches. Now I know none of that is your problem but you did ask for comments and I am sure others will have the same issue. I realise a fully modular Boost had its advantages but I am hopeful it will sit alongside a big fat integration-tested all of Boost distro too... Pete