Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_pkg/e7083019d663b7ef03eea370995dd6c56f128c55
commit
e7083019d663b7ef03eea370995dd6c56f128c55
[log]
author
tonyaiuto <tony.aiuto@gmail.com>
Thu Apr 10 22:48:39 2025 -0400
committer
GitHub <noreply@github.com>
Thu Apr 10 22:48:39 2025 -0400
tree
6552e65df41e2fb92bd1bf76e6fba78c052fae2d
parent
cd7e10846f97b5cb9b184c87b4ceaf2f1b4b5d3f [diff]
parent
5695833d592242b6c07a9f891c31b1461f23e019 [diff]
feat: support raw symlinks from declare_symlink() (#930)

Using the `ctx.actions.declare_symlink()` API, rules can create explicit
symlinks to arbitrary
paths, which Bazel will keep as symlinks. The packaging logic treats
these
as regular files, so tries to read through them and store the content
they point to. This
is incorrect for two reasons: they are supposed to be left as symlinks
and may be dangling
symlinks from the perspective of packaging.

To fix, introduce a new type of file entry: `raw_symlink`. These entries
mean the `src` is
a symlink whose stored path should be stored into the destination
verbatim, also as a symlink.
Such artifacts are identified using `File.is_symlink`, a Bazel 8+ API.

Work towards https://github.com/bazelbuild/rules_pkg/issues/929
tree: 6552e65df41e2fb92bd1bf76e6fba78c052fae2d
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. distro/
  5. doc_build/
  6. docs/
  7. examples/
  8. pkg/
  9. tests/
  10. toolchains/
  11. .bazelignore
  12. .bazelrc
  13. .gitignore
  14. .pre-commit-config.yaml
  15. .typos.toml
  16. AUTHORS
  17. BUILD
  18. CHANGELOG.md
  19. CODEOWNERS
  20. CONTRIBUTING.md
  21. CONTRIBUTORS
  22. deps.bzl
  23. developers.md
  24. LICENSE
  25. mappings.bzl
  26. MODULE.bazel
  27. patching.md
  28. pkg.bzl
  29. README.md
  30. version.bzl
  31. WORKSPACE
  32. 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