What we really need is: a) https://bugs.gentoo.org/162450 to avoid scaring users; b) possibly some level of QA notice to distinguish between "check this out" (think e.g. qa-vdb LHS where it _might_ be unused, but not necessarily), and "this is definitely wrong" I am convinced we need a), I am not-at-all convinced we need b) - at least not in terms of whether bugs are reported.
AFAIS https://bugs.gentoo.org/162450 is not implemented.
Maybe
we can agree that the qa-warnings in vdr-eclass make more sense
if i change them to "eawarn" or "einfo"?
In my opinion, most plugins in the vdr context will practically not develop any further anyway. It is more important to keep the current status of vdr-software in the ecosystem up to date as well as possible.
So I need a practical useful
approach instead of a fundamental discussion please.