Jakob Borg 65aaa607ab Use Go 1.5 vendoring instead of Godeps ... Change made by: - running "gvt fetch" on each of the packages mentioned in Godeps/Godeps.json - `rm -rf Godeps` - tweaking the build scripts to not mention Godeps - tweaking the build scripts to test `./lib/...`, `./cmd/...` explicitly (to avoid testing vendor) - tweaking the build scripts to not juggle GOPATH for Godeps and instead set GO15VENDOREXPERIMENT. This also results in some updated packages at the same time I bet. Building with Go 1.3 and 1.4 still *works* but won't use our vendored dependencies - the user needs to have the actual packages in their GOPATH then, which they'll get with a normal "go get". Building with Go 1.6+ will get our vendored dependencies by default even when not using our build script, which is nice. By doing this we gain some freedom in that we can pick and choose manually what to include in vendor, as it's not based on just dependency analysis of our own code. This is also a risk as we might pick up dependencies we are unaware of, as the build may work locally with those packages present in GOPATH. On the other hand the build server will detect this as it has no packages in it's GOPATH beyond what is included in the repo. Recommended tool to manage dependencies is github.com/FiloSottile/gvt.		2016-03-05 21:21:24 +01:00
..
bench_test.go	Use Go 1.5 vendoring instead of Godeps	2016-03-05 21:21:24 +01:00
memdb_suite_test.go	Use Go 1.5 vendoring instead of Godeps	2016-03-05 21:21:24 +01:00
memdb_test.go	Use Go 1.5 vendoring instead of Godeps	2016-03-05 21:21:24 +01:00
memdb.go	Use Go 1.5 vendoring instead of Godeps	2016-03-05 21:21:24 +01:00