Robert Ramey wrote:
If it were done via tar balls the procedure would look something like the following:
a) There would be one tar ball per library. I guess that means that if done today that would mean around 118 libraries.
... You seem to have missed the bpm discussions, Robert, so here's the "announcement": http://lists.boost.org/Archives/boost/2015/01/218757.php http://lists.boost.org/Archives/boost/2015/01/218891.php Reading about Beman's experience may be of value too: http://lists.boost.org/Archives/boost/2015/01/218934.php bpm doesn't quite work the way you envisage, in that the user doesn't run a dependency checker locally to determine what needs to be installed (as the dependency checker can't actually dependency-check something that isn't installed yet). Instead, when you say "bpm install serialization", it downloads a pre-created module dependency graph and then downloads and installs whatever the graph says are serialization's dependencies. Give bpm a go and you'll hopefully get a feel for what we're (seemingly endlessly) talking about.