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
When a project features main-package applications in cmd directories, have go get automatically recurse from the top-level repository down into each cmd descendant and go install these nodes as well.
The current way to force this is to explicitly append /... to the URL for go get. Would be more convenient and consistent to do this by default.
The text was updated successfully, but these errors were encountered:
The inconsistency is not between directories so much as between library code vs. application code. go get with a top-level repository path obtains all the code necessary for importing code, but neglects to install any Go applications. This omission doesn't happen in other languages, where gem install, cabal install, npm install are sure to setup source code as well as applications during installation.
bradfitz
changed the title
go get: recurse by default
proposal: cmd/go: make 'go get' recurse by default
Feb 21, 2018
When a project features main-package applications in cmd directories, have go get automatically recurse from the top-level repository down into each cmd descendant and go install these nodes as well.
The current way to force this is to explicitly append
/...
to the URL for go get. Would be more convenient and consistent to do this by default.The text was updated successfully, but these errors were encountered: