1 |
i implemented eclass checking for some of the most common ones in the tree, |
2 |
but Zac didn't particularly care for the maintaining of lists of functions |
3 |
used by eclasses directly in repoman (due to the concern of them getting out |
4 |
of sync). |
5 |
|
6 |
so the proposal is to utilize the existing eclass documentation markers to |
7 |
extract the complete list of functions provided by an eclass. the upside is |
8 |
the metadata stays current, and we can scale better to all eclasses w/out |
9 |
requiring manual intervention. the downside is that if people don't properly |
10 |
document their eclasses, repoman might throw false positives (warnings, not |
11 |
errors) about unused eclasses being inherited, and will miss throwing errors |
12 |
when functions are used but the respective eclasses aren't inherited. |
13 |
|
14 |
however, i think that's a good hammer to throw at eclass maintainers to keep |
15 |
their documentation up-to-date and accurate. any other opinions/feedback ? |
16 |
-mike |