| commit | 5ecaeb5c535c114db04219c35cd921abdf63d8f9 | [log] [tgz] |
|---|---|---|
| author | Alex Eagle <alex@aspect.dev> | Tue Jul 18 10:21:50 2023 -0700 |
| committer | Alex Eagle <alex@aspect.dev> | Tue Jul 18 11:01:26 2023 -0700 |
| tree | 9af8b2b14876341f7602fba4a860c16d6e306219 | |
| parent | 2fd7f9138c366e58ae88e53fb3efc12fd584786c [diff] |
chore: update docs
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