You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2019. It is now read-only.
This is more of a request for discussion rather than an issue. I find the dep sub-commands to be quite inconsistent in behaviour with each other and with the go compiler. Here's my suggestion, I'm sure there are holes in it, but I just want to start a discussion.
Proposed behavior
$ cd MyProject
$ mkdir -p ./src/my-package
$ export GOPATH=`pwd`
# write some code...
# initializes dep in my-package, .toml and .lock reside in ./src/my-package
# location based on "$GOPATH/src/$PKG/Gopkg.toml"
$ dep init my-package
# ensures deps in my-package (assumes ./src/my-package/Gopkg.toml, .lock)
$ dep ensure my-package
# updates deps in my-package (assumes ./src/my-package/Gopkg.toml, .lock)
$ dep ensure my-package -update
# prune deps in my-package (assumes ./src/my-package/Gopkg.toml, .lock)
$ dep prune my-package
# same as current cd ./src/my-package; dep status package-list...
$ dep status my-package -pkg=[packages list...]
godep version output
dep:
version : devel
build date :
git hash :
go version : go1.9.1
go compiler : gc
platform : darwin/amd64
go version output
go version go1.9.2 darwin/amd64
The text was updated successfully, but these errors were encountered:
nbosscher
changed the title
Consistency in command line tool
Consistent way to reference Gopkg.toml in command line tool
Mar 6, 2018
nbosscher
changed the title
Consistent way to reference Gopkg.toml in command line tool
Consistent way to reference Gopkg.toml in cli
Mar 6, 2018
nbosscher
changed the title
Consistent way to reference Gopkg.toml in cli
Consistent way to reference Gopkg.toml in CLI
Mar 6, 2018
This is more of a request for discussion rather than an issue. I find the dep sub-commands to be quite inconsistent in behaviour with each other and with the go compiler. Here's my suggestion, I'm sure there are holes in it, but I just want to start a discussion.
Proposed behavior
godep version
outputgo version
outputThe text was updated successfully, but these errors were encountered: