1 |
In terms of QA, unintentional transitive eclass usage is generally bad. |
2 |
This occurs when an ebuild uses functionality from an eclass it doesn't |
3 |
directly inherit. It would be useful for eclasses that allow certain |
4 |
transitive usage (e.g. various python eclasses) to be able to tag that |
5 |
relationship internally so tools can make use of that data. |
6 |
|
7 |
Along those lines, pkgcheck now has eclass doc parsing support which |
8 |
allows scanning ebuilds for missing, indirect, or unused eclass inherits |
9 |
as well as internal eclass function usage. In order to more closely |
10 |
report valid indirect inherit results, some tag including this data |
11 |
needs to be included for eclasses allowing this relationship. |
12 |
|
13 |
What do interested parties think about including an optional eclass doc |
14 |
tag such as '@TRANSITIVE_INHERITS:' or other similar name in eclasses |
15 |
that allow this? The tag value would be a space-separated list of |
16 |
allowed transitive inherits for the given eclass. |
17 |
|
18 |
Tim |