Now, here's the question: what did the folks who were asking for this
functionality actually want to use the information for?
I should stress that it's overkill for extracting subsets of Boost, because
many libraries will depend on just one or two files inside boost/mpl or
boost/preprocessor, so using the list for that purpose will result in an
even "thicker" dependency than copying with bcp already produces.
It's possible to contract the above list even further: for example by
contracting to library names where possible, so for example contracting all
boost/regex.hpp boost/regex libs/regex
to just "regex"
However there would still be a lot of Boost headers that can't automatically
be assigned to any library name, so it's not clear to me how much use this
If folks can give me an idea of what they were looking to use a dependency
list for it'll help me decide whether to stop here or to continue trying to
contract the list further.