At Mon, 7 Feb 2011 09:26:22 -0000, John Maddock wrote:
There is something deeply flawed about the modularization design if it requires a switch to CMake.
Modularization doesn't *require* a switch to CMake at all. There's no reason the modularized boost couldn't be used with Boost.Build, provided someone was willing to make the (relatively minor) Jamfile changes that would be necessary.
If we organize like the sandbox,
Last I looked, there was no real organization there. Or, there were at least two organizations: http://svn.boost.org/svn/boost/sandbox/boost/library-name http://svn.boost.org/svn/boost/sandbox/libs/library-name which is unsustainable, and http://svn.boost.org/svn/boost/sandbox/library-name/boost/ http://svn.boost.org/svn/boost/sandbox/library-name/libs/ The planned/proposed organization is roughly like the latter. If you want to look at the organization in detail, see https://github.com/boost-lib/boost -- Dave Abrahams BoostPro Computing http://www.boostpro.com