Commit Graph

7 Commits (27edaf84f1acd37c96936ccd1a643479a3d61a8c)

Author SHA1 Message Date
Tim Hockin 16a33318b7 Use a valid address for swagger 2015-08-18 21:50:27 -07:00
Eric Paris 8f3577e5d2 Do not use goimports in hack/update-generated-conversions.sh
Stop depending on an external binary needing to be on people's system.
Use the code directly.
2015-08-13 19:37:01 -04:00
Eric Paris 00929ed7d8 Convert generated-deep-copies to use golang.org/x/tools/imports
I don't like users to need an external binary which can easily get out
of sync. Just include the tools.
2015-08-13 19:36:57 -04:00
Eric Paris ce6f2c8e4b Do not build genconversion and gendeepcopy twice
The hack/after-build/verify-* functions were using the hack/update-*
functions.  Which means that if you call hack/verify-* you will do the
build twice. Stop it.
2015-08-12 10:05:48 -04:00
Muhammed Uluyol eba19cc96a Add missing argument to function call and don't set GOPATH directly 2015-08-11 21:54:37 -07:00
Muhammed Uluyol 567bb15432 Generate conversions/deep-copies for experimental. Currently we make (and register) duplicate functions but this is benign. 2015-08-11 17:12:24 -07:00
Eric Paris 3b7c39656c Split hack/{verify,update}-* files so we don't always go build
Right now some of the hack/* tools use `go run` and build almost every
time. There are some which expect you to have already run `go install`.
And in all cases the pre-commit hook, which runs a full build wouldn't
want to do either, since it just built!

This creates a new hack/after-build/ directory and has the scripts which
REQUIRE that the binary already be built. It doesn't test and complain.
It just fails miserably. Users should not be in this directory. Users
should just use hack/verify-* which will just do the build and then call
the "after-build" version. The pre-commit hook or anything which KNOWS
the binaries have been built can use the fast version.
2015-08-11 14:20:46 -04:00