This document collects thoughts and notes about vgo from the Gophers #vgo channel. Invites to Gophers Slack from here.
The initial paper can be read here https://research.swtch.com/vgo.
The reference implementation: https://go.googlesource.com/vgo/ and mirrored on Github here: https://github.com/golang/vgo.
The Go issue tracker is used to track bugs / feature requests for vgo. The issue titles need to start with x/vgo so that they can be automatically categorized. You can read the existing issues here.
Currently vgo is in active development / prototype phase. It has some rough edges, changes will happen at a rapid pace. You are encouraged to try vgo and give your feedback, share your experience with it, and contribute to it.
For any production workloads, use dep, or migrate to it if you have not done so already.
vgo will be merged in the Go tree and replace dep at a later date.
These are threads that have been created from the initial reference manifest for vgo:
golang-nuts ML: Go += Package Versioning, vgo and vendoring
golang-dev ML: https://groups.google.com/forum/#!topic/golang-dev/MNQwgYHMEcY
HackerNews posts: https://news.ycombinator.com/from?site=swtch.com
| Question | Answer |
|---|---|
| Hitting GitHub API rate limits? | Create a token and add it to .netrc, see related issue |
| How does vgo handles dependencies of older, discarded versions link? | https://github.com/zeebo/vgo-test-version-selection |
| Why are major versions in import paths? | https://groups.google.com/forum/#!topic/golang-dev/Plc42fslQEk |
How to go get so that I can run a program, not download a library? | https://gophers.slack.com/archives/C9BMAAFFB/p1519687366000101 |