The rules to declare licenses and their kinds should be in a distinct bazel package from the ones that consume them. #85
Assignees
Labels
Comments
aiuto
added a commit
to aiuto/rules_license
that referenced
this issue
Jun 3, 2023
…es_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 bazelbuild#85 cleanup. Bonus: Fix the rule so it does not do a double write.
1 task
aiuto
added a commit
to aiuto/rules_license
that referenced
this issue
Jun 3, 2023
- It does nothing that useful, and does not actually work yet. - It relies on the older, get_licenses_info, API. Part of bazelbuild#85
This was referenced Jun 3, 2023
|
This is mostly done in 0.0.7. Not closed yet until we delete all the forwarders that were left behind. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are too many things in the
rulespackage.The expected use case is that everyone is going to by declaring a
licenserule, but fewer people will be using those to produce license audit or SBOMs. Most of the people who do produce an SBOM are expected to check rules_license into their repo and modify or reuse as appropriate, so having a clear separation between the packages you modify and the ones you leave alone is helpful.The text was updated successfully, but these errors were encountered: