| commit | 9ab275bde8fe1bb887642e9250b8d58aba11af61 | [log] [tgz] |
|---|---|---|
| author | Paul Jolly <paul@myitcv.io> | Tue Jun 26 08:45:55 2018 +0100 |
| committer | Tuo Shan <shantuo@google.com> | Wed Jun 27 22:11:37 2018 +0000 |
| tree | 74df1831ca2705ed956a27c7e5f7c316515a92e6 | |
| parent | 574849d519ec3acb591fc5620ee0aa3ea48081e0 [diff] |
gosrc: add minimal support for vgo-aware modules Currently, gddo assumes that there will be just one go-import HTML meta tag when resolving a custom import's VCS repository. vgo introduces a special new go-import meta tag to identify the location of published Go modules; it has the VCS identifier 'mod'. https://golang.org/issue/25140 and https://golang.org/issue/25139 added minimal awareness to the Go 1.9 and 1.10 branches for the vgo transition that will start in Go 1.11. Part of this backported support is to ignore the module special go-import meta tag which has a 'mod' vcvs type: https://go-review.googlesource.com/c/go/+/115298/4/src/cmd/go/internal/get/discovery.go Per https://golang.org/issue/25069, the 'mod' vcs type is used by 'new' Go code to identify where published modules can be fetched. As a first minimal step we can make gddo "aware" in the same way that Go 1.9 and 1.10 are "aware" of these published modules by simply ignoring that go-import meta tag. Later gddo CLs will likely need to enhance support for vgo, but this is a sufficient first step. Fixes #558 Change-Id: Ibddfcc8e0a663792da206a244e5cffb8c68fe894 Reviewed-on: https://go-review.googlesource.com/120817 Reviewed-by: Tuo Shan <shantuo@google.com>