14914 2022-09-15 19:42:22 +0000 Add DISTRO_FEATURES to enable ptests to use valgrind and more 2025-02-14 16:48:12 +0000 1 1 7 Build System, Metadata & Runtime OE-Core oe-core other 4.2 x86 Multiple RESOLVED WONTFIX Medium enhancement 4.2 1 Zheng.Qiu unassigned randy.macleod richard.purdie ross.burton sgw --- --- Yes (doc changes required) oldest_to_newest 94032 0 Zheng.Qiu 2022-09-15 19:42:22 +0000 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 94055 1 richard.purdie 2022-09-22 14:36:40 +0000 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. 94102 2 randy.macleod 2022-10-03 13:36:08 +0000 Closing since there isn't interest in enabling such tests as a DISTRO_FEATURE. PACKAGECONFIG can work. 100960 3 randy.macleod 2025-02-14 16:46:21 +0000 bulk change to add Saul's non-WR address. 101030 4 randy.macleod 2025-02-14 16:48:12 +0000 Bulk change: Remove Saul's old WR address.