Modular Boost Frequently Asked Questions

Conversion to Git and modular Boost

What is the role, if any, of Ryppl and CMake in the Boost modularization plan?

None. Modularization + the move to Git is a big enough change to be done separately and to stand on its own merits.

What role, if any, does the old Boost sandbox play in modular Boost?

None. The whole need for the sandbox as a part of the boost repository goes away. Proposed libraries that used to go in the sandbox now just go in their own public repositories. They are typically hosted on ​GitHub, but any public host will do. ExtractSandbox shows how to move a library from the old sandbox to GitHub. StartModDev shows how a repository for a proposed library would work.

Is it possible to checkout only library A and its prerequisites?

Not automatically. Automatic dependency resolution is planned for the future, but not as a part of the conversion to Git and modular Boost.

So how do I get a modularized Boost that I can actually use?

See these instructions,

General Questions

How do I get write access to my library at github.com/boost-lib?

See Administrative Privileges for public library repositories.

How do I submit fixes to a Boost library owned by someone else?

The Git community has a usual way of submitting changes upstream. See ​GitHub's description of the process. ​Stackoverflow also covers the topic. This ​video shows how GitHub manages interactions between the submitter and the library owner.