When writing the ptest for jq in meta-oe(1), we initially had valgrind be a dependency. Ross pointed put out that: "Not sure this is useful for us: we want to use ptest for integration testing, not development regression testing" so we removed the valgrind dependency. Randy and I discussed this, and thought that for released products being able to run valgrind and other tools that check for correct runtime behaviour would be useful, for example a user added a number of complicated CVEs. This enhancement suggest add DISTRO_FEATURES:ptest-extended. 1: https://lists.openembedded.org/g/openembedded-devel/messages?expanded=1&msgnum=98823
You can make an arguments to make almost any PACKAGECONFIG a distro feature and I'm not sure we want to go that route, particularly as in some cases you may want to enable it but not for others. As such I'd suggest making it a PACKAGECONFIG. If we do ever have a lot of places we need to track a list, we'd probably create an include file.
Closing since there isn't interest in enabling such tests as a DISTRO_FEATURE. PACKAGECONFIG can work.
bulk change to add Saul's non-WR address.
Bulk change: Remove Saul's old WR address.