use sys.exit() instead of exit() (#844)

This is a cherry-pick of an upstream change. The
hermetic Python toolchain that Kleaf uses does
not have the exit builtin. To use pkg_install(),
temporarily cherry-pick this change.

Bug: 324907235
Change-Id: Ie5c73b0a11e5158295c6cff25d4e7950663f4b24
(cherry picked from commit e14245aa9653b462f60a9f202d25fd5956983e03)
2 files changed
tree: 688a68141052f3df8c1426fe9c27a34da08fcfa2
  1. .bazelci/
  2. deb_packages/
  3. distro/
  4. doc_build/
  5. docs/
  6. examples/
  7. pkg/
  8. tests/
  9. toolchains/
  10. .bazelignore
  11. .gitignore
  12. AUTHORS
  13. BUILD
  14. CHANGELOG.md
  15. CODEOWNERS
  16. CONTRIBUTING.md
  17. CONTRIBUTORS
  18. deps.bzl
  19. developers.md
  20. install.bzl
  21. LICENSE
  22. mappings.bzl
  23. METADATA
  24. MODULE.bazel
  25. MODULE_LICENSE_APACHE2
  26. OWNERS
  27. package_variables.bzl
  28. patching.md
  29. pkg.bzl
  30. providers.bzl
  31. README.md
  32. rpm.bzl
  33. version.bzl
  34. WORKSPACE
  35. 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.

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