"godep get" command about godep

[kr]

Yes! I've been meaning to open an issue for this for a while.

Thanks for bringing this up!

I think it should be called godep get, since it has to do more
than just invoke the go tool in a sandbox. The behavior I'm
currently imagining, for the command godep get foo:

1. It runs go get -d foo
2. It runs cd $(go list -f {{.Dir}} foo) && godep go install foo

[kr]

See also #6.

[kr]

I edited the description above to say "godep get".

But if you really like the "godep go get" form (or something else),
please say so. I'm very much open to bikeshed painting. :)

[kr]

It's not quite as simple as the two steps I described above, because
the arguments might specify multiple packages. So it would probably
have to expand the package list first, then do those two steps for
each package (and maybe this could be optimized to avoid redundant
work).

[kr]

I also want "godep get" to to The Right Thing even if the specified package
doesn't use godep at all. It should gracefully fall back to behaving equivalently
to whatever "go get" does.

[mreiferson]

I agree with all of the above 👍