9465272c28
This helps ensure that `github.com/docker/docker/pkg/...` is actually safe to use in isolation (ie, doesn't import anything from `github.com/docker/docker` except other things from `pkg` or vendored dependencies). Adding `github.com/docker/docker/utils` to the imports of `pkg/version/version.go`: ``` ---> Making bundle: validate-pkg (in bundles/1.7.0-dev/validate-pkg) These files import internal code: (either directly or indirectly) - pkg/version/version.go imports github.com/docker/docker/autogen/dockerversion - pkg/version/version.go imports github.com/docker/docker/utils ``` And then removing it again: ``` ---> Making bundle: validate-pkg (in bundles/1.7.0-dev/validate-pkg) Congratulations! "./pkg/..." is safely isolated from internal code. ``` Signed-off-by: Andrew "Tianon" Page <admwiggin@gmail.com> |
||
|---|---|---|
| .. | ||
| .build-deb | ||
| .build-rpm | ||
| .resources-windows | ||
| .dockerinit | ||
| .dockerinit-gccgo | ||
| .ensure-emptyfs | ||
| .ensure-frozen-images | ||
| .ensure-httpserver | ||
| .go-autogen | ||
| .go-compile-test-dir | ||
| .integration-daemon-setup | ||
| .integration-daemon-start | ||
| .integration-daemon-stop | ||
| .validate | ||
| README.md | ||
| binary | ||
| build-deb | ||
| build-rpm | ||
| cover | ||
| cross | ||
| dynbinary | ||
| dyngccgo | ||
| gccgo | ||
| test-docker-py | ||
| test-integration-cli | ||
| test-unit | ||
| tgz | ||
| ubuntu | ||
| validate-dco | ||
| validate-gofmt | ||
| validate-pkg | ||
| validate-test | ||
| validate-toml | ||
| validate-vet | ||
README.md
This directory holds scripts called by make.sh in the parent directory.
Each script is named after the bundle it creates. They should not be called directly - instead, pass it as argument to make.sh, for example:
./hack/make.sh test
./hack/make.sh binary ubuntu
# Or to run all bundles:
./hack/make.sh
To add a bundle:
- Create a shell-compatible file here
- Add it to $DEFAULT_BUNDLES in make.sh