cybercyst/go
1
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-05-05 15:43:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated GOPATH (markdown)

Constantine A. Murenin 2019-01-16 13:21:39 -06:00
parent 25e6f4abb1
commit f274773600
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
GOPATH.md

@ -48,9 +48,9 @@ As a result, if (from your repository project) you import a package that is in t
Even though the GOPATH may be a list of directories, it is generally sufficient to use a single GOPATH for all Go code on your machine. Since all packages retrieved with "go get" have a unique URL (and thus a unique path on disk), having more than one GOPATH is almost never necessary when building with the Go tool.
### Use of `vendor` directories
### The `vendor` directories
Note that as of go 1.11, the `vendor` directories are only supported when `$PWD` is a subset of `GOPATH`; see issue 29670 and https://stackoverflow.com/questions/54140415/go-1-11-ignores-the-vendor-directory-the-errors-give-the-impression-the-direc/54156547#54156547.
Note that as of go 1.11, the `vendor` directories are only supported when `$PWD` is under `GOPATH`; see https://github.com/golang/go/issues/29670 and https://stackoverflow.com/questions/54140415/go-1-11-ignores-the-vendor-directory-the-errors-give-the-impression-the-direc/54156547#54156547.
## FAQ
### Why won't ` $GOPATH/src/cmd/mycmd/*.go ` build?