23cd9d7b05
Automatic merge from submit-queue Rename root BUILD to BUILD.bazel, and rename build-tools/ back to build/ **What this PR does / why we need it**: undoes #35453. `build-tools/` was intended to be a temporary workaround until https://github.com/bazelbuild/bazel/issues/552 was fixed, which is has been, as of bazel 0.4.1. **Which issue this PR fixes**: fixes #38126 FYI @thockin since this is likely to be rebase hell, my list of actions: ```console $ git mv BUILD BUILD.bazel $ git commit -a $ git mv build-tools/ build/ $ sift -l 'build-tools' | xargs sed -i -e 's:build-tools/:build/:g' $ git checkout HEAD docs/ $ git commit -a ``` |
||
|---|---|---|
| .. | ||
| src/k8s.io/client-go | ||
| README.md | ||
| copy.sh | ||
| godeps-json-updater.go | ||
README.md
This staging/src/k8s.io/client-go directory is the staging area of the client repo. It contains a versioned client, tools built around the client like the reflector, and all the client dependencies. The content will be periodically published to k8s.io/client-go repo.
The staged content is copied from the main repo, i.e., k8s.io/kubernetes, with directory rearrangement and necessary rewritings. To sync the content with the latest code in your local k8s.io/kubernetes, you need to run godep restore in k8s root directory, then run staging/copy.sh.
vendor/k8s.io/client-go is a symlink pointing to this staging area, so to use the packages in the staging area, you can import it as "vendor/client-go/", as if the client were vendored. The client will be vendored from k8s.io/client-go for real after the test matrix is converted to vendor k8s components.