friendlyelec
/
rk35xx-android14
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '602f7ebbd6'
${ noResults }
rk35xx-android14/external/bazelbuild-rules_license/examples
History
hmz007 36ed224bac
Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 		1 year ago
..
manifest Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
my_org/licenses Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
policy_checker Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
sboms Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
src Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
vndor Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
BUILD Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago
README.md Rockchip Anroid14_SDK 20240628-rkr5 (2556df1a) 1 year ago

README.md

Examples for rules_license

This set of files provides an example of how license rules can be used.

Terminology

  • Organization: A company, organization or other entity that wants to use license rules to enforce their particular compliance needs. These examples use the work organization throughout.
  • SCM: source code management system. These examples assume that an organization has a SCM that can enforce ownership restrictions on specific folder trees. Targets are divided into BUILD files that are reviewed by engineers vs. those that are reviewed by an organizations compliance team.

Overview