Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_pkg/261bb4942ac792011566408d8f98981ac02775fb
commit
261bb4942ac792011566408d8f98981ac02775fb
[log] [tgz]
author
Mark Reuter <13319190+reutermj@users.noreply.github.com>
Tue Mar 17 12:16:29 2026 -0700
committer
GitHub <noreply@github.com>
Tue Mar 17 15:16:29 2026 -0400
tree
4f801d287c764edc994c820170b5159a87e41047
parent
5449272ab5b112cc27d83d5e6fd8840cb345ee9a [diff]
Support relocatable rpmbuild by adding data attribute to the toolchain (#1047)

* Support relocatable rpmbuild by adding data attribute to the toolchain

rpmbuild ships with runtime configuration files (lib/rpm/) that must be
present for it to successfully build RPMs. When running under remote
execution, these files were not being staged because the toolchain had
no way to declare them as dependencies.

Add a `data` attribute to `rpmbuild_toolchain` so that runtime files
can be specified alongside the rpmbuild binary. These files are
propagated through `RpmbuildInfo` and included as inputs to the MakeRpm
action in `pkg_rpm`.
7 files changed
tree: 4f801d287c764edc994c820170b5159a87e41047
  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