8 Dec
2013
8 Dec
'13
12:09 p.m.
Actually, thinking about it some more, this doesn't look as a good approach at all. First, the develop branch for the submodules becomes unneeded by the superproject. Individual developers may use it at their discretion but it doesn't matter in the big picture.
And why is that a bad thing? The only purpose of the superproject is as a way of tracking releasable states of the whole library collection.
what about library dependencies? if lib X depends on a certain version of lib Y? iiuc this information is stored in the superproject as well? in a way i fear the modularized boost is not exactly bisect-friendly, or does git-bisect traverse submodules?