On 20/05/15 07:59 PM, Peter Dimov wrote:
That is, Boost.Build itself is absolutely standalone, but not all Boost.Build releases will work with a given Boost release.
Which is very likely why distributions package Boost.Build from the Boost release, instead of using a standalone release - it's guaranteed to be compatible.
I understand. So if Boost.Build were to released stand-alone, dependent packages (such as the fictional Boost-without-BB or Boost.Python) would have to test what (earliest) version of Boost.Build will work (assuming future Boost.Build releases will remain compatible, which is another serious concern), and then document that requirement appropriately. This is all doable, and other package have done this forever. Stefan -- ...ich hab' noch einen Koffer in Berlin...