Manage dependencies via luthier #111
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've already hit a wall with git-subrepo in #105 because subrepos interact awfully with submodules. All of this is miserable, and I think we're going to go the way that every mid-sized C++ project with dependencies must go to stay sane: embracing their own bespoke tool. As such, I've replaced the check-in for every dependency here with a
foo.tune
file inextern
that describes the remote source and the tag that we would like to check out, andluthier
now has the ability to fetch dependencies. It will do this as part of aconfigure
step, but you can also invoke it directly with thefetch
subcommand.