| commit | 59a0658f891a82cc8b4c37a62d06abef08bc7aa4 | [log] [tgz] |
|---|---|---|
| author | Filippo Valsorda <hi@filippo.io> | Sat Sep 05 03:13:21 2015 +0100 |
| committer | Filippo Valsorda <hi@filippo.io> | Sat Sep 05 03:13:21 2015 +0100 |
| tree | 3aa90fb9a2aba25ed9ef4e71f94a0f1356743f47 | |
| parent | 11fcff82296c1945c1105c94fc173fe76ffa72d9 [diff] |
Update README.md
gvt is a simple Go vendoring tool made for the GO15VENDOREXPERIMENT.
It's based entirely on gb-vendor.
You run gvt fetch when you would run go get. gvt downloads packages to ./vendor/.... With GO15VENDOREXPERIMENT=1 set the compiler will find and use those dependencies without import path rewriting. gvt works recursively as you would expect, and lets you update vendored dependencies. It also writes a manifest to ./vendor/manifest.
Packages whose dependencies are vendored with gvt are go build-able and go get-able by Go 1.5 with GO15VENDOREXPERIMENT=1 set.
go get -u github.com/FiloSottile/gvt
$ gvt fetch github.com/fatih/color
2015/09/05 02:38:06 fetching recursive dependency github.com/mattn/go-isatty
2015/09/05 02:38:07 fetching recursive dependency github.com/shiena/ansicolor
$ tree -d
.
└── vendor
└── github.com
├── fatih
│ └── color
├── mattn
│ └── go-isatty
└── shiena
└── ansicolor
└── ansicolor
9 directories
$ cat > main.go
package main
import "github.com/fatih/color"
func main() {
color.Red("Hello, world!")
}
$ export GO15VENDOREXPERIMENT=1
$ go build .
$ ./hello
Hello, world!
$ gvt update github.com/fatih/color
Full usage on GoDoc 
There are many Go vendoring tools, but they all have some subset of the following problems
go get