From b18b93197c201e6df2b47d9728ee4af42bcc4ba9 Mon Sep 17 00:00:00 2001 From: Bryce Kwon Date: Sat, 7 Nov 2026 11:14:17 -1000 Subject: Say why the Lua search paths reach the tests --- tests/extensions/lib.sh | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'tests/extensions') diff --git a/tests/extensions/lib.sh b/tests/extensions/lib.sh index 041a042..addc10e 100644 --- a/tests/extensions/lib.sh +++ b/tests/extensions/lib.sh @@ -3,7 +3,10 @@ # beside this file, lists the standalone Lua interpreters the checks can run # under, and offers a probe that asks the Lua inside the cgit binary itself # whether a module is available to it, since that interpreter can differ from -# every standalone one on the path. +# every standalone one on the path. LUA_PATH, LUA_CPATH and their versioned +# forms come through from the environment on purpose, as they are how a +# system points Lua at its modules, so the probes find what the system has. +# A fallback that needs a module gone runs through without_lua_modules. EXTENSIONS_DIRECTORY=$(cd "$TEST_OUTPUT_DIRECTORY/../custom/extensions" && pwd) EXT_TEST_DIRECTORY=$(cd "$TEST_OUTPUT_DIRECTORY/extensions" && pwd) -- cgit 2.12.1