Closed Tornskaden closed 3 years ago
Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!
It makes sense for me to have projects outside of
GOPATH
and symlink the folders.I understand you have an env var
DEPPROJECTROOT
which needs to be set per project. I do not want to remember where the project's folder is symlinked each time I want to rundep status
ogdep ensure
I even want a convenient way to rundep init
when outside theGOPATH
Having to run
DEPPROJECTROOT=/real/path/to/project/which/I/keep/forgetting dep ensure
is inconvenient. So is settingDEPPROJECTROOT
in.bashrc
or.zshrc
when working on more than one project on the same machine.There may be a smart way to pipe an env var from a file, but my bash mojo is not Jedi enough
My suggestion
Let ´dep´ look for env vars in a
.dep
file, in the directory and its ancestors. With aDEPPROJECTROOT=/real/path/to/project
inside.dep
, one can simply rundep init
or one of the other commands. With aDEPWORKSPACE=/real/path/to/workspace
inside.dep
, one can rundep init foobar
from the workspace holding local projects.E.g. in
~/development/playground/golang/foobar
the.dep
file can containDEPPROJECTROOT=~/go/src/playground/foobar
Or~/development/playground/golang
could hold a.dep
file containingDEPWORKSPACE=~/go/src/playground
Similarly~/development/worlddomination/golang
could hold a.dep
file containingDEPWORKSPACE=~/go/src/github.com/<username>