Clean up @bazel_tools
#8859
Labels
P3
We're not considering working on this, but happy to review a PR. (No assignee)
stale
Issues or PRs that are stale (no activity for 30 days)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: process
Comments
aiuto
added
team-Bazel
dslomov
added
team-OSS
philwo
added
P3
bazel-io
pushed a commit
that referenced
this issue
Aug 29, 2019
This target globs all bzl files under @bazel_tools//tools under a single filegroup. Progress toward #8859 Should fix bazelbuild/skydoc#185 when we introduce a bzl_library target in bazel_skylib to point to this new target. RELNOTES: None. PiperOrigin-RevId: 266219278
|
Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem / feature request:
This is an umbrella issue to track efforts to clean up
@bazel_tools. We should remove unnecessary source code from this repo, and make it work forbazel query @bazel_tools//....Details
This repo is built into Bazel. It's always available in every workspace. It's a place for commonly used tools like
tools/test/test-setup.sh, which is the test wrapper used for everybazel testaction.But there is also source code in this repo, each file for their own reason. E.g. the runfiles libraries
@bazel_tools//tools/<lang>/runfilesare included as source so they can be compiled into binaries.Some source code's purpose in
@bazel_toolsis less obvious. Sometimes they cause problems, like #8614 whose culprit is #8742 (comment).What's the output of
bazel info release?release 0.28.0The text was updated successfully, but these errors were encountered: