The use case is one that I've run into since the git transition and doing Predef development. And recently I also see it in the BPL development. For Predef my normal way to work on it is to clone *only* the Predef repo as it's an entirely standalone library (doesn't depend on anything). Then I have a jamroot file above the cloned Predef, as it's required to build anything with BBv2. It's easy enough for me to do this of course. But I would like to make it easier for *users* to just get the Predef library and say, run tests and build without special instructions or having the whole of the Boost super project. But at the same time I can't just include a jamroot in the Predef project because it would break (in silent and strange ways) when it's part of the Boost super project.

Boost Python would also like to operate in such a standalone mode for development. And I want to support that model. But having the requirement makes it harder for that support to happen as there extra steps the developer and user have to do to create that jamroot.

In other words.. I would like to support getting one of the Boost libraries, and assuming I have its requirements (both source and tools), I can interact with it without changes. One example of such an interaction would be running tests on cloud CI services.

 

I'm failing to understand that sentence.. Or if there's a question in there :-(