You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,7 @@ The Ebuild we have since `0.97.0`, as soon as I know that at least one user is a
130
130
### `app-misc/homeassistant-full`
131
131
132
132
WARNING: This one currently breaks (caused by shell limitations) emerge with an 'Argument list too long' error. It compiles with a [kernel hack](https://git.edevau.net/onkelbeh/HomeAssistantRepository/issues/190#issuecomment-1002). Thanks to @gcampagnoli.
133
-
This Ebuild contains USE Flags for (nearly) all components of Home Assistant with external dependencies. Most components compile, but these are too many (for me) to run tests for all of them on a regular schedule. It holds **983** USE Flags.
133
+
This Ebuild contains USE Flags for (nearly) all components of Home Assistant with external dependencies. Most components compile, but these are too many (for me) to run tests for all of them on a regular schedule. It holds **982** USE Flags.
134
134
135
135
A list of all components aka USEFlags is generated with every release [DOMAINTABLE.md](DOMAINTABLE.md)
136
136
@@ -606,12 +606,12 @@ A daily compile test is run at Github with Python 3.9 to catch general faults. E
606
606
607
607
## Licenses
608
608
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.
609
-
There are 1827 Ebuilds in total, 1816 of them have in total 1837 (42 different) licenses assigned.
609
+
There are 1832 Ebuilds in total, 1821 of them have in total 1842 (42 different) licenses assigned.
610
610
611
611
|License| Ebuilds using it|
612
612
|-------|-----|
613
-
|MIT|1050|
614
-
|Apache-2.0|401|
613
+
|MIT|1051|
614
+
|Apache-2.0|405|
615
615
|GPL-3|107|
616
616
|BSD|106|
617
617
|LGPL-3|25|
@@ -653,9 +653,9 @@ There are 1827 Ebuilds in total, 1816 of them have in total 1837 (42 different)
653
653
|GPL-2+|1|
654
654
|GPL-2-with-linking-exception|1|
655
655
656
-
(Last counted: 13/05/2024)
656
+
(Last counted: 14/05/2024)
657
657
658
658
I did my best to keep these clean. If a valid license was published on PyPI, it has been automatically merged. Otherwise I took it from GitHub or alternatively from comments/files in the source. Sometimes these differed and have been not unique. All license strings are adjusted to the list in `/usr/portage/gentoo/licenses/`. Some packages do not have any license published. In this case, Authors have been asked for clarification, some did not respond. Following the [official Gentoo Guide](https://devmanual.gentoo.org/general-concepts/licenses/index.html), these then were added with an `all-rights-reserved` license and `RESTRICT="mirror"` was set. Find the appropriate licenses referenced in the Ebuild files and in the corresponding homepages or sources.
659
659
660
660
A big thanks goes to Iris for reviewing this README.
0 commit comments