fix(test): `package_naming_aggregate_test` on Windows

The test was failing on Windows:
```
==================== Test output for //tests:package_naming_aggregate_test:
ls: cannot access 'C:/[...]/bin/tests/package_naming_aggregate_test.exe.runfiles/_main/tests/test_naming_some_value.deb': No such file or directory
================================================================================
```
It tried to directly access files in the `runfiles` directory, but on
Windows Bazel uses by default a manifest file instead of creating actual
symlinks.

The change consists in adding a minimalistic version of the
[rlocation()](https://github.com/bazelbuild/rules_shell/blob/main/shell/runfiles/runfiles.bash)
helper function that:
- when set, reads from `$RUNFILES_MANIFEST_FILE` to resolve paths,
- otherwise uses `$TEST_SRCDIR` directly, as before.

This allows to enable the test in Windows CI now it passes.

Note on the stricter error handling:
- `set -u` is to fail fast should any of the expected `TEST_*`
  environment variables be unbound,
- `set -o pipefail` is to fail fast should either side of the
  `grep | cut` pipe fail.
2 files changed
tree: 09a61bd2dc69eb00985cf4fd01f1c16443c1bccd
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. contrib/
  5. distro/
  6. doc_build/
  7. docs/
  8. examples/
  9. pkg/
  10. tests/
  11. toolchains/
  12. .bazelignore
  13. .bazelrc
  14. .gitignore
  15. .pre-commit-config.yaml
  16. .typos.toml
  17. AUTHORS
  18. BUILD
  19. CHANGELOG.md
  20. CODEOWNERS
  21. CONTRIBUTING.md
  22. CONTRIBUTORS
  23. deps.bzl
  24. developers.md
  25. LICENSE
  26. mappings.bzl
  27. MODULE.bazel
  28. patching.md
  29. pkg.bzl
  30. README.md
  31. version.bzl
  32. WORKSPACE
  33. WORKSPACE.bzlmod
README.md

Bazel package building

Bazel rules for building tar, zip, deb, and rpm for packages.

For the latest version, see Releases (with WORKSPACE setup) / Documentation

Use rules-pkg-discuss@googlegroups.com for discussion.

CI: Build status

Basic rules

Package building rules

  • pkg - Rules for building packages of various types.
  • examples - Cookbook examples for using the rules.

As of Bazel 4.x, Bazel uses this rule set for packaging its distribution. Bazel still contains a limited version of pkg_tar but its feature set is frozen. Any new capabilities will be added here.

WORKSPACE setup

Sample, but see releases for the current release.

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "rules_pkg",
    urls = [
        "https://mirror.bazel.build/github.com/bazelbuild/rules_pkg/releases/download/0.9.1/rules_pkg-0.9.1.tar.gz",
        "https://github.com/bazelbuild/rules_pkg/releases/download/0.9.1/rules_pkg-0.9.1.tar.gz",
    ],
    sha256 = "8f9ee2dc10c1ae514ee599a8b42ed99fa262b757058f65ad3c384289ff70c4b8",
)
load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
rules_pkg_dependencies()

To use pkg_rpm(), you must provide a copy of rpmbuild. You can use the system installed rpmbuild with this stanza.

load("@rules_pkg//toolchains/rpm:rpmbuild_configure.bzl", "find_system_rpmbuild")

find_system_rpmbuild(
    name = "rules_pkg_rpmbuild",
    verbose = False,
)

MODULE.bazel setup

bazel_dep(name = "rules_pkg", version = "0.0.10")

To use pkg_rpm(), you must provide a copy of rpmbuild. You can use the system installed rpmbuild with this stanza.

find_rpm = use_extension("//toolchains/rpm:rpmbuild_configure.bzl", "find_system_rpmbuild_bzlmod")
use_repo(find_rpm, "rules_pkg_rpmbuild")
register_toolchains("@rules_pkg_rpmbuild//:all")

For developers

We hold an engineering status meeting on the first Monday of every month at 10am USA East coast time. Add to calendar / meeting notes