exclude coverage from shellcheck
This commit is contained in:
parent
795eaa7ffe
commit
ed11e957e8
2
.github/workflows/shellcheck.yml
vendored
2
.github/workflows/shellcheck.yml
vendored
@ -21,4 +21,4 @@ jobs:
|
||||
SHELLCHECK_OPTS: -s bash -e SC2034 -e SC2016
|
||||
with:
|
||||
additional_files: '*.ebuild'
|
||||
ignore_paths: opencv pillow numpy protobuf
|
||||
ignore_paths: coverage numpy opencv pillow protobuf
|
||||
|
@ -524,12 +524,12 @@ A daily compile test is run at Github with Python 3.9 to catch general faults. E
|
||||
|
||||
## Licenses
|
||||
This repository itself is released under GPL-3 (like most Gentoo repositories), all work on the depending components under the licenses they came from. Perhaps you came here because I filed an issue at your component about a bad or missing license. It is easy to [assign a license](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository). During cleanups and license investigations I have been asked often which license to choose. I am not a lawyer, but I can offer the following table, counted over this repository, perhaps this helps your decision. If a package has more than one license listed, all of them are counted.
|
||||
There are 1769 Ebuilds in total, 1762 of them have in total 1768 (35 different) licenses assigned.
|
||||
There are 1770 Ebuilds in total, 1763 of them have in total 1769 (35 different) licenses assigned.
|
||||
|
||||
|License| Ebuilds using it|
|
||||
|-------|-----|
|
||||
|MIT|1081|
|
||||
|Apache-2.0|315|
|
||||
|Apache-2.0|316|
|
||||
|GPL-3|108|
|
||||
|BSD|99|
|
||||
|LGPL-3|28|
|
||||
|
Loading…
x
Reference in New Issue
Block a user