commit | d313c8bf754960af0cf147e47b554b03a1db8de7 | [log] [tgz] |
---|---|---|
author | Greg Magolan <gmagolan@gmail.com> | Thu Jan 04 08:16:59 2024 -0800 |
committer | GitHub <noreply@github.com> | Thu Jan 04 08:16:59 2024 -0800 |
tree | d9e6323a4bee5dee206f28ceb38c15d2555cb691 | |
parent | 71260d8669eed2b39e0d15e243d1a6f0df310090 [diff] |
fix: move flags that should only be set with bazel 6 to bazel6.bazelrc recommended settings (#711)
Base Starlark libraries and basic Bazel rules which are useful for constructing rulesets and BUILD files.
This module depends on bazel-skylib. In theory all these utilities could be upstreamed to bazel-skylib, but the declared scope of that project is narrow and it‘s very difficult to get anyone’s attention to review PRs there.
bazel-lib is just a part of what Aspect provides:
Installation instructions are included on each release: https://github.com/aspect-build/bazel-lib/releases
To use a commit rather than a release, you can point at any SHA of the repo.
For example to use commit abc123
:
url = "https://github.com/aspect-build/bazel-lib/releases/download/v0.1.0/bazel-lib-v0.1.0.tar.gz"
with a GitHub-provided source archive like url = "https://github.com/aspect-build/bazel-lib/archive/abc123.tar.gz"
strip_prefix = "bazel-lib-0.1.0"
with strip_prefix = "bazel-lib-abc123"
sha256
. The easiest way to do this is to comment out the line, then Bazel will print a message with the correct value.Note that GitHub source archives don't have a strong guarantee on the sha256 stability, see https://github.blog/2023-02-21-update-on-the-future-stability-of-source-code-archives-and-hashes