Skip to content
Bazel rules for creating packages of many types (zip, tar, deb, rpm, ...)
Python Go Shell
Branch: master
Clone or download
laurentlb and aiuto Remove glob pattern that doesn't match anything (#109)
Fix for Bazel flag --incompatible_disallow_empty_glob
Latest commit b28e8c8 Oct 28, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
deb_packages Start adding rules to create packages to rules_pkg. (#26) Jun 6, 2019
examples
pkg Remove glob pattern that doesn't match anything (#109) Oct 28, 2019
.gitignore
.travis.yml Add basic travis-ci tests Dec 28, 2017
AUTHORS Add deb_packages ruleset Dec 28, 2017
BUILD add example for using deb_packages rules Dec 28, 2017
CODEOWNERS
CONTRIBUTING.md initial commit Dec 21, 2017
CONTRIBUTORS initial commit Dec 21, 2017
LICENSE initial commit Dec 21, 2017
README.md

README.md

Bazel package building & fetching rules

Bazel rules for packaging and fetching (for Debian and other distribution channels).

There is currently no distinct discussion group for these rules. Use bazel-dev@googlegroups.com.

Travis CI
Build Status

Basic Rules

Package Building Rules

  • pkg - Rules for building packages of various types.

WORKSPACE Rules

  • deb_packages - fetch deb files from Debain style mirror servers

Helper tools

Background

These rules originated in the distroless project as well as discussions about the goal of that project and are intended as a way to retrieve bundled software packages from various places.

The initial scope is currently targeting Debian style distributions, because the Bazel docker rules allow optional deb and tar files to be included in their container images. That work was done in December 2017.

We are currently (June 2019) in the process of migrating the Bazel packaging rules from Bazel to this repo. Tracking issue: https://github.com/bazelbuild/bazel/issues/8489.

Plan

  • DONE: slight refactor and fixup of existing package fetching rules.
  • DONE: copy rules from https://github.com/bazelbuild/bazel/tools/build_defs/pkg.
  • DONE: refactor this repo so that package fetching rules have distinct WORKSPACE requirements.
  • DONE: get them working
  • integrated with federation CI.
  • migrate rules shipped with Bazel to this rule set.
  • migrate Bazel distribution packaging to use this rule set.
  • innovate wildly.

The last 4 steps may overlap in time.

You can’t perform that action at this time.