cmd/go/internal/vgo: prefer module path from Godeps/Godeps.json over GOPATH

The entry in Godeps/Godeps.json is explicitly what we're looking for:
the import path of the root directory.

The logic about deriving a module path from the current directory's
location in GOPATH should usually match, but it's less a direct statement:
for example, maybe a fork has been checked out.

If the two disagree, prefer Godeps/Godeps.json's explict statement.

Change-Id: I439684f5d34eeaf41419bbdae82139ba79498f6c
Reviewed-on: https://go-review.googlesource.com/121858
Reviewed-by: Bryan C. Mills <bcmills@google.com>
3 files changed
tree: a0e8857cc735e6b4afc7167e797f80ed15e825a2
  1. AUTHORS
  2. CONTRIBUTING.md
  3. CONTRIBUTORS
  4. LICENSE
  5. PATENTS
  6. README.md
  7. codereview.cfg
  8. main.go
  9. vendor/
README.md

Versioned Go Prototype (vgo)

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.

Download/Install

Use go get -u golang.org/x/vgo.

You can also manually git clone the repository to $GOPATH/src/golang.org/x/vgo.

Report Issues / Send Patches

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.