3 ms·

I love the ability to go get things... but from a multi-component perspective, go-get doesn't really work with our environment, specifically the notion of multi

by cik 11y ago

I love the ability to go get things... but from a multi-component perspective, go-get doesn't really work with our environment, specifically the notion of multiple deploy keys, private repositories or hyper-componentized go codebases. So, our awesome co-op wrote gigo. Over time, we'll extend it (or hey, pull request!) it to do other, better things. But for now, it makes fetching private repositories a breeze, in the laziest/happiest way we could possibly think of. Hope someone else finds this useful.

cik 11y ago
I'm going to reply to myself, since a friend asked about vendoring. Our current flow is just to privately (and occasionally publicly) fork something that we care about - to solve the vendoring issue. I could easily see vendoring original sources for builds within gigo, that way we use something like bruise to make it easy to support a virtualenv-like thing for golang. But today, that's not the problem we had.