python-jmespath: install jp as a non-byte-compiled command

Upstream ships its jp command-line tool as a plain "jp.py" script. Under
that name OpenWrt byte-compiles it into a non-executable /usr/bin/jp.pyc
(and the -src package keeps a "#!/usr/bin/env python" jp.py, which has no
interpreter on OpenWrt), so it fails the CI generic executable check.

Install it as /usr/bin/jp instead: the missing .py extension stops it from
being byte-compiled and Python3/FixShebang rewrites the shebang to
/usr/bin/python3. Add a test-version.sh override since jp takes a required
expression argument and has no version flag for the generic check to probe.

Signed-off-by: Alexandru Ardelean <alex@shruggie.ro>
This commit is contained in:
Alexandru Ardelean
2026-06-07 14:37:59 +03:00
committed by Alexandru Ardelean
parent ba593bc0f3
commit e7aff35e97
3 changed files with 30 additions and 1 deletions
@@ -0,0 +1,16 @@
#!/bin/sh
# shellcheck shell=busybox
# The jp command-line tool takes a required expression argument and has no
# version flag, so the generic version check cannot detect the version from it.
# The version is covered by the import check in test.sh instead.
case "$PKG_NAME" in
python3-jmespath | python3-jmespath-src)
exit 0
;;
*)
echo "Untested package: $PKG_NAME" >&2
exit 1
;;
esac