Allows creating symlinks in the created download repositories.

This is especially useful for cross-platform creation of symlinks.

Matthew Clarkson authored Dec 13, 2023 and Matthew Clarkson committed Feb 13, 2024

When a tool such as `//abc.sh` is provide. In nested projects it
was being resolved to the full label with the workspace.

This patch checks if the workspace is the same as the provided label,
if so do not add the workspace.

`use_repo_rule` never made it into Bazel 6.4.0

Individual `defs.bzl` files allow a fine-grained load graph for
Bazel so it only has to load `.bzl` files that it needs to.

This is much better than a single `defs.bzl` that pulls in all
the different `load` statements.

`rules_toolchain` is now open-source 🎉

Double down on all hermetic tooling should be provided in `tools`.

`rules_coreutils` should be the ruleset that provides hermetic coreutils,
not `rules_download`.

Users should only pay for what they use and if they never use core utilities,
we download it everytime.

Especially, turning off legacy runfiles.

Allows running commands using hermetically provided binaries:

```py
archive = use_repo_rule("@rules_download//download:defs.bzl", "download_archive")

archive(
    ...,
    commands = {
        "symlink": ["ln", "-s", "abc", "foo"],
    },
)
```

`use_repo_rule` is available in `6.4.0` and above.

It _hugely_ simplifies what we want to do.

That should be the new minimum version for our rulesets.

As of writing, `6.4.0` is not released. The release candidates do not have
the `use_repo_rule` added, yet. Most rules use `last_rc` Bazel version.

`visibility` is available in 6.0+.

Sebastian Birunt authored Oct 02, 2023 and Matthew Clarkson committed Feb 13, 2024

`deb` can use also `zstd` compression next to `XZ`.

This provides a convienient way to unpack the actual data contained
in a Debian package. This has a extensive use-case in grabbing pre-built
binaries for use in Debian based open-container images.

Lukasz Okraszewski authored Sep 26, 2023 and Matthew Clarkson committed Feb 13, 2024

This change makes it so that if the user does not know the
intergrity when adding a new download, the framework will
notify them with the correct intergrity on the first download.

This is a better DevEx as otherwise the user needs to manually
download and checksum the file first.

This approach will also fail more gracefully when using mirrors
that have dynamically generated files and cannot be easily pinned.

We get syntax highlighting and `pre-commit`.

`git` is line based, having each argument on a separate line allows
tracking changes with `git blame`