David Abrahams wrote:
A few days ago I started thinking about the implications of giving each Boost library a separate subtree of the repository, and it led me to some interesting places.
* Start with the assumption that each library has a boost/ directory containing its subset of the headers it currently has. So, for example, Boost.Python would have
boost/ python.hpp python/ ...
where "..." above is identical to the current contents of $BOOST_ROOT/boost/python/
* Our release process would merge the boost/ directories
* To test a library from a source distribution, you'd need to get the boost/ directories of any libraries it depends on into the #include path.
Right. A fallout of this is that it all in a sudden becomes easy to test a development snapshot of a single library against all prerequisite libraries being from some stable state. Yay for modularity. Regards, Stefan -- ...ich hab' noch einen Koffer in Berlin...