Google Git
Sign in
fuchsia / third_party / github.com / bazelbuild / rules_license / 03230b8c3f8773e684cae2afd74fa7310623b142
commit03230b8c3f8773e684cae2afd74fa7310623b142[log] [tgz]
authorTony Aiuto <aiuto@google.com>Sat Jun 03 00:08:56 2023 -0400
committerTony Aiuto <aiuto@google.com>Sat Jun 03 00:13:45 2023 -0400
treed973fb3205bee31c2c04a255f275b273ab814176
parent27c9be72d2285755f90ffd0920ea9020939d682e [diff]
Move licenses_used from rules/compliance.bzl to sample_reports/licenses_used.bzl

licenses_used is really an example of how the rules can work. As such it is really to be used for examples and as a reference implementation for people to build their own reports from.

This is part of the #85 cleanup.

Bonus: Fix the rule so it does not do a double write.
7 files changed
tree: d973fb3205bee31c2c04a255f275b273ab814176
  1. .bazelci/
  2. .github/
  3. admin/
  4. distro/
  5. doc_build/
  6. docs/
  7. examples/
  8. licenses/
  9. rules/
  10. rules_gathering/
  11. sample_reports/
  12. tests/
  13. tools/
  14. .gitignore
  15. BUILD
  16. CODEOWNERS
  17. deps.bzl
  18. LICENSE
  19. MODULE.bazel
  20. README.md
  21. version.bzl
  22. WORKSPACE
  23. WORKSPACE.bzlmod
README.md

rules_license

CI: Build status

This repository contains a set of rules and tools for

  • declaring metadata about packages, such as
    • the licenses the package is available under
    • the canonical package name and version
    • copyright information
    • ... and more TBD in the future
  • gathering those license declarations into artifacts to ship with code
  • applying organization specific compliance constriants against the set of packages used by a target.
  • (eventually) producing SBOMs for built artifacts.

WARNING: The code here is still in active initial development and will churn a lot.

If you want to follow along:

Background reading: These is for learning about the problem space, and our approach to solutions. Concrete specifications will always appear in checked in code rather than documents.