qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-17 23:54:51 -07:00
Code Releases Activity

cmd/go: document where get writes, and not vendor directories

Browse Source 
Fixes #12260.

Change-Id: I95c27aad6de8064b9a205d4ee507bce75926f16d
Reviewed-on: https://go-review.googlesource.com/17948
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This commit is contained in:
Russ Cox 2015-12-17 01:00:14 -05:00
parent 8fac7e3cc7
commit f474885f8a
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/cmd/go/alldocs.go
View File

@ -497,6 +497,10 @@ missing packages but does not use it to look for updates to existing packages.
Get also accepts build flags to control the installation. See 'go help build'. Get also accepts build flags to control the installation. See 'go help build'.
When checking out a new package, get creates the target directory
GOPATH/src/<import-path>. If the GOPATH contains multiple entries,
get uses the first one. See 'go help gopath'.
When checking out or updating a package, get looks for a branch or tag When checking out or updating a package, get looks for a branch or tag
that matches the locally installed version of Go. The most important that matches the locally installed version of Go. The most important
rule is that if the local installation is running version "go1", get rule is that if the local installation is running version "go1", get
@ -507,6 +511,8 @@ Unless vendoring support is disabled (see 'go help gopath'),
when go get checks out or updates a Git repository, when go get checks out or updates a Git repository,
it also updates any git submodules referenced by the repository. it also updates any git submodules referenced by the repository.
Get never checks out or updates code stored in vendor directories.
For more about specifying packages, see 'go help packages'. For more about specifying packages, see 'go help packages'.
For more about how 'go get' finds source code to For more about how 'go get' finds source code to

6
src/cmd/go/get.go
View File

@ -45,6 +45,10 @@ missing packages but does not use it to look for updates to existing packages.
Get also accepts build flags to control the installation. See 'go help build'. Get also accepts build flags to control the installation. See 'go help build'.
When checking out a new package, get creates the target directory
GOPATH/src/<import-path>. If the GOPATH contains multiple entries,
get uses the first one. See 'go help gopath'.
When checking out or updating a package, get looks for a branch or tag When checking out or updating a package, get looks for a branch or tag
that matches the locally installed version of Go. The most important that matches the locally installed version of Go. The most important
rule is that if the local installation is running version "go1", get rule is that if the local installation is running version "go1", get
@ -55,6 +59,8 @@ Unless vendoring support is disabled (see 'go help gopath'),
when go get checks out or updates a Git repository, when go get checks out or updates a Git repository,
it also updates any git submodules referenced by the repository. it also updates any git submodules referenced by the repository.
Get never checks out or updates code stored in vendor directories.
For more about specifying packages, see 'go help packages'. For more about specifying packages, see 'go help packages'.
For more about how 'go get' finds source code to For more about how 'go get' finds source code to