Most software packages require some kind of installation process. For Boost, it has been the "Getting started" process documented on the web site. With modularization, some of the details of "Getting Started" will change. Why are you concerned that some of those installation process details ensures that user and developer scripts and setups continue to work?
I've had a lot of trouble to get boost.build+bjam to compile the assembler code from boost.context. I'm annoyed that I get some additonal burden to re-write this stuff for the new build env again because the old one will not work with the modularized boost. I think this is not a good migration strategy. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de