Beman Dawes wrote:
As far as I can see, scaling Boost up to a much larger number of libraries implies decentralization and decoupling, probably in the form of per-library modules or something similar.
100 % aggree with this.
Modularization seems to have been missed in the discussions of Subversion, Git, and Mercurial. Do distributed version control systems in general and Git in particular have any important advantages/disadvantages over svn for highly modularized projects?
Hmmm - if boost is "modularized" - wouldn't that mean that each library has it's own repository. Or that each developer can decide where he want's to store his version? I would think that the testing/deployment process could update/export each library from a different place without much problem. Robert Ramey.