The usual layout is to put your project's repo inside the src directory
in your GOPATH. In your case, that would mean something like
Inside that directory, you'd have .git and some .go source files, and
maybe a subdirectory or two if you have more than one package in the
repo. You'll set GOPATH to some constant value in your ~/.profile
(in this case export GOPATH=~/gopath), and never think about it
or change it again. So far, this is not specific to godep, just general
Go code layout.
The godep save command operates on packages, similar to most
of the go tool commands. If you give no arguments, it uses ".", and
otherwise it takes one or more import paths to scan. This means
you'll usually run godep save from the same place you run go install,
and this is typically at the repo root.
Example project: https://github.com/kr/go-heroku-example
(There's actually very little in that repo that's specific to Heroku.)
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts...@googlegroups.com
> For more options, visit https://groups.google.com/groups/opt_out