| commit | 203abfb0741bf96c7c5e8dab019f6fe9c89bded3 | [log] [tgz] |
|---|---|---|
| author | Russ Cox <rsc@golang.org> | Wed Jun 06 16:40:30 2018 -0400 |
| committer | Russ Cox <rsc@golang.org> | Thu Jun 07 13:26:29 2018 +0000 |
| tree | 27f90c0abd3150cd1004d99a8e496097af5606d4 | |
| parent | 20f1cf1cd2db95dab9392c26138149e131911a29 [diff] |
cmd/go/internal/vgo: fix handling of vendor dir in package patterns A directory x/vendor containing code is just a package called vendor. A directory x/vendor/y is vendored code. When a package pattern scans the current module's file tree it should include a package called vendor but should not include the directories containing vendored code. Maybe related to a comment on golang/go#25624. Change-Id: I083a98a9c70c2121cff7a2f394ff985a54bed37a Reviewed-on: https://go-review.googlesource.com/116759 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
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.