| commit | 9797cd1414faeb61e4c18b7c2459e6e9d1db635f | [log] [tgz] |
|---|---|---|
| author | Filippo Valsorda <filippo@cloudflare.com> | Wed Sep 16 01:29:51 2015 +0100 |
| committer | Filippo Valsorda <filippo@cloudflare.com> | Wed Sep 16 01:29:51 2015 +0100 |
| tree | 3f2b874c265037c6b2e07e1b2dad6fc1cf8e1e0d | |
| parent | 1c871863af500cad558a91c775c0626df457279d [diff] |
Improve 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 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. Finally, it strips the VCS metadata so that you can commit the vendored source cleanly.
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
You know how to use go get? That's how you use gvt fetch.
$ 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!
$ git add main.go vendor/ && git commit
Full usage on GoDoc 
There are many Go vendoring tools, but they all have some subset of the following problems
go get