Julian Gonggrijp wrote:
PROPOSAL
The following (evolutionary) global changes to Boost should be planned and given priority over any other proposals [e.g. 5], in the following order:
1. Reduction of dependencies between Boost libraries. 2. Simple but effective automation of dependency handling.
We all agree on these goals in principle, but what do you actually propose
we need to do? We need to start somewhere. Specifics are needed.
What I can contribute at the moment is
- a suggestion that we publish a Boost dependency report in HTML format
somewhere on boost.org that tells us, and anyone interested, what depends on
what and why;
- a program that generates such a report (in plain text) as a starting point
(attached).
As an example, I've pasted inline the output of "boostdep smart_ptr".
This only gives the primary dependencies; it would be nice for the finished
product to include the secondary module dependencies as well (without going
into specifics what included what, just what module brought up the secondary
dependency).
Dependencies for smart_ptr:
align: