Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_pkg/0343f018f980d35a3fe856a08646e1c2704ed6a2
commit
0343f018f980d35a3fe856a08646e1c2704ed6a2
[log]
author
tonyaiuto <tony.aiuto@gmail.com>
Sun Feb 22 14:35:09 2026 -0400
committer
GitHub <noreply@github.com>
Sun Feb 22 14:35:09 2026 -0400
tree
920fd5783f6c2e3b875d73fd098c3267fd81d1ee
parent
3504fe0689b95a73fec427beeaac84d6be4b9c8c [diff]
parent
c16df15ae877101fca35bea47de5167046e2ce9c [diff]
Bring testing for bzlmod vs. non-bzlmod up to date with bazel features (#1029)

Bring testing for bzlmod vs. non-bzlmod up to date with bazel features.

Head and LTS have bzlmod enabled by default, so:
- stop enabling the flag explicitly
- stop calling out "bzlmod" in the test name, that is now assumed, only
nobzlmod needs naming

- Do the packaging test against workspace only for bazel 7 and earlier.
- we probably could drop the workspace test entirely. It is essentially
meaningless now

This is a spin out from a followup PR to #1027. //distro:packaging_test
was failing on workspace tests while using bazel 8.x. Since that seemed
strange, I decided to clean this up now, to get a little better prepared
for the day that `--enable_bzlmod` is no longer a valid flag.
tree: 920fd5783f6c2e3b875d73fd098c3267fd81d1ee
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. contrib/
  5. distro/
  6. doc_build/
  7. docs/
  8. examples/
  9. pkg/
  10. providers/
  11. tests/
  12. toolchains/
  13. .bazelignore
  14. .bazelrc
  15. .gitignore
  16. .pre-commit-config.yaml
  17. .typos.toml
  18. AUTHORS
  19. BUILD
  20. CHANGELOG.md
  21. CODEOWNERS
  22. CONTRIBUTING.md
  23. CONTRIBUTORS
  24. deps.bzl
  25. developers.md
  26. LICENSE
  27. mappings.bzl
  28. MODULE.bazel
  29. patching.md
  30. pkg.bzl
  31. README.md
  32. version.bzl
  33. WORKSPACE
  34. 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