suricata: improve PACKAGECONFIG[unittests] control

Allow downstream users to explicitly select desired PACKAGECONFIG
options (e.g. via "=").

Users are currently forced to use ":remove" (with "ptest").

Signed-off-by: Clayton Casciato <majortomtosourcecontrol@gmail.com>
Signed-off-by: Scott Murray <scott.murray@konsulko.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/recipes-ids/suricata/suricata_7.0.13.bb b/recipes-ids/suricata/suricata_7.0.13.bb
index b0d2c82..936c057 100644
--- a/recipes-ids/suricata/suricata_7.0.13.bb
+++ b/recipes-ids/suricata/suricata_7.0.13.bb
@@ -46,8 +46,8 @@ PACKAGECONFIG ??= "file \
                    cap-ng \
                    net \
                    ${@bb.utils.filter('DISTRO_FEATURES', 'seccomp', d)} \
+                   ${@bb.utils.contains('DISTRO_FEATURES', 'ptest', 'unittests', '', d)} \
                    "
-PACKAGECONFIG:append = " ${@bb.utils.contains('DISTRO_FEATURES', 'ptest', 'unittests', '', d)}"
 
 PACKAGECONFIG[pcre2] = "--with-libpcre2-includes=${STAGING_INCDIR} --with-libpcre2-libraries=${STAGING_LIBDIR}, ,libpcre2 ,"
 PACKAGECONFIG[yaml] = "--with-libyaml-includes=${STAGING_INCDIR} --with-libyaml-libraries=${STAGING_LIBDIR}, ,libyaml ,"