lmdb-test ships /usr/bin/mtest, a stress test that unconditionally
opens ./testdb in the current directory and aborts (SIGABRT) when
that directory is missing. In the CI runtime container that's
always the case, so the framework's --version probe ends up with
"Aborted" output, no PKG_VERSION match, and the package gets
reported as "Generic tests failed - No executables in the package
provided version 0.9.35".
Add libs/lmdb/test-version.sh that handles each sub-package by name:
lmdb (library) and lmdb-test (no usable version probe) pass the
override, lmdb-utils runs 'mdb_dump -V' and matches against
PKG_VERSION, and unknown sub-packages fail loudly to force this
script to be updated. The other generic checks (no hardcoded paths,
stripped, linked libs) still run for every binary.
Signed-off-by: Alexandru Ardelean <redacted>
--- /dev/null
+#!/bin/sh
+
+pkg=$1
+ver=$2
+
+case "$pkg" in
+lmdb)
+ exit 0
+ ;;
+lmdb-test)
+ exit 0
+ ;;
+lmdb-utils)
+ mdb_dump -V 2>&1 | grep -qF "LMDB $ver" || exit 1
+ exit 0
+ ;;
+*)
+ echo "test-version.sh: unhandled sub-package '$pkg'" >&2
+ exit 1
+ ;;
+esac