diff options
| author | Russ Cox <rsc@golang.org> | 2019-04-30 16:04:50 -0400 |
|---|---|---|
| committer | Russ Cox <rsc@golang.org> | 2019-05-09 00:01:25 +0000 |
| commit | 856b57e0d42f104e762b5df7701133c0aef4dc5f (patch) | |
| tree | ae5b89e9db1d484a454a38a5baf086c7e0d8734b /src/go.mod | |
| parent | 41df5aeb7f02a47ff7ccf5002140b70b04a4fd46 (diff) | |
| download | go-856b57e0d42f104e762b5df7701133c0aef4dc5f.tar.gz go-856b57e0d42f104e762b5df7701133c0aef4dc5f.zip | |
cmd/go: diagnose go.mod and vendor out of sync in std and cmd
The most common failure mode of the current std/cmd setup is
going to be people running "go get m@latest" and then not running
"go mod vendor" and being confused about getting the old m.
Diagnose and report what to do.
Also, having done the check, when in the standard library,
switch the go command to -mod=vendor mode.
This avoids some network accesses I saw when running
'go clean -modcache' before doing some work in cmd.
Change-Id: I0ba4a66637b67225a9b97a1c89f26f9015b41673
Reviewed-on: https://go-review.googlesource.com/c/go/+/174528
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Bryan C. Mills <bcmills@google.com>
Diffstat (limited to 'src/go.mod')
| -rw-r--r-- | src/go.mod | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/go.mod b/src/go.mod index a527f9a244..0d2bd16284 100644 --- a/src/go.mod +++ b/src/go.mod @@ -7,5 +7,4 @@ require ( golang.org/x/net v0.0.0-20190424112056-4829fb13d2c6 golang.org/x/sys v0.0.0-20190425145619-16072639606e // indirect golang.org/x/text v0.3.2 // indirect - golang.org/x/tools v0.0.0-20190425214124-2d660fb8a000 // indirect ) |