On 4 June 2015 at 19:56, Peter Dimov
Daniel James wrote:
I've had no problem dealing with the numeric modules. The output of 'git config -f .gitmodules -l' contains pretty much everything you need to know.
...
If you're trying to find modules by walking the filesystem, you'll just create problems for yourself.
Walking the filesystem produces better results in the following cases:
- when you have manually placed a (proposed) library in libs/ that is not yet a submodule - when you have a Boost directory structure that has no Git metadata
In these cases, why does your tool need to understand git modules?
- or when you have a Boost directory that doesn't have all the libraries in libs/ but just a subset
That's easily dealt with. You just check that the module is present.