Maybe this is hypocritical, but I actually tend to advocate for keeping things in one big repo, when you have that option :) (http://programmers.stackexchange.c

Maybe this is hypocritical, but I actually tend to advocate for keeping things in one big repo, when you have that option :) (http://programmers.stackexchange.com/a/236567 http://programmers.stackexchange.com/a/236567) I don't think anything beats having all you need in one git log. But if you want external projects to pull down your code and build against it, that's exactly what peru is designed to do. I mentioned this in another comment, but one of the things we haven't nailed down yet is transitive dependencies: A depends on B which depends on C, etc. If you start playing with peru, I'd love to get feedback on how you think that should work. (The most obvious way would be like git submodules, but I'm not sure how we want to handle multiple copies of the same dependency.)