| commit | 9ba9f10d104595a66a90556e12f08355f5a75f00 | [log] [tgz] |
|---|---|---|
| author | Elias Naur <elias.naur@gmail.com> | Mon Feb 26 16:04:08 2018 +0100 |
| committer | Russ Cox <rsc@golang.org> | Thu Apr 05 15:50:01 2018 +0000 |
| tree | 77a5dfdc433693ee7b703fca39826bac9b0e42a9 | |
| parent | 890b798475a0fc2108fa88d9b2810d5f768f5752 [diff] |
vendor/cmd/go/internal/vgo: refer to GOPATH when no module is found When FindModulePath gives up its search for a module in the current directory, it complains with the message "vgo: cannot determine module path for legacy source directory <dir> (outside GOROOT, no import comments)" Since FindModulePath is really searching through GOPATH, change the reference in the error message to match. While here, delete the word "legacy". It is confusing in the common case of simply running vgo in the wrong directory. Change-Id: Iba2b3e15233c373e978bcff43c98530fc74b9a50 Reviewed-on: https://go-review.googlesource.com/97195 Reviewed-by: Russ Cox <rsc@golang.org>
This repository holds a prototype of what the go command might look like with integrated support for package versioning.
See research.swtch.com/vgo for documents about the design.
Use go get -u golang.org/x/vgo.
You can also manually git clone the repository to $GOPATH/src/golang.org/x/vgo.
See CONTRIBUTING.md.
This is still a very early prototype. You are likely to run into bugs. Please file bugs in the main Go issue tracker, golang.org/issue, and put the prefix x/vgo: in the issue title.
Thank you.