packages/lang/lua, branch master

lua: install a pkg-config file for Lua 5.4

2026-10-06T07:40:22Z

Lua stopped shipping a pkg-config file after 5.1; the 5.2, 5.3 and 5.4 release tarballs contain none. Distributions add one to their Lua packages instead: Debian's liblua5.4-dev ships lua5.4.pc, lua-5.4.pc and lua54.pc, Alpine's lua5.4-dev ships lua5.4.pc and lua-5.4.pc. Build systems of Lua consumers look Lua 5.4 up under these names. The package stages no pkg-config file so far, so such builds cannot find liblua5.4; the only Lua pkg-config file in the staging directory is lua.pc of the lua package (5.1.5). Stage lua5.4.pc, generated from a template with the package version, and lua-5.4.pc and lua54.pc as links to it. It points to the headers in /usr/include/lua5.4 and to liblua5.4, and lists libm and libdl as private libraries for static linking, as the upstream Makefile links them on Linux. Of the packages that look up one of these names through pkg-config, libinput disables its Lua plugin support explicitly in the previous commit. tio looks up lua-5.4 before lua but depends on lua (5.1), so it links liblua5.4 without depending on it until the next commit moves it to Lua 5.4. The others select their Lua version explicitly, look up lua (5.1) first, build without the feature using Lua, or depend on lua5.4 already. Assisted-By: Claude Opus 5.5 Signed-off-by: Mirko Vogt

lua: drop the lua5.4 LUA_ROOT patch

2026-10-06T07:40:22Z

luaconf.h builds the module search paths out of LUA_ROOT, which upstream hardcodes to /usr/local, where nothing installs on OpenWrt. LUA_ROOT is defined unconditionally, but the two macros it feeds, LUA_PATH_DEFAULT and LUA_CPATH_DEFAULT, are both guarded with #if !defined and are the only users of it, so set them in TARGET_CFLAGS and drop the patch. The resulting paths are the ones the patch produced, so the interpreter behaves exactly as before. Signed-off-by: Alexandru Ardelean

lua: use LUA_INSTALL_DIR in cqueues, lua-ffi and luaossl

2026-10-06T07:40:22Z

The three Lua variants of each package install the same files, differing only in the destination directory, so define LUA_INSTALL_DIR next to the other per-variant settings and share a single install recipe. Same idiom as luafilesystem, luasec and luaexpat. No packaged path changes. Signed-off-by: Alexandru Ardelean

luaossl: fix Lua 5.4 module installation paths

2026-10-05T09:01:29Z

Commit 3fe92e63f558 moved the default Lua 5.4 module search paths from /usr/local to /usr. luaossl still staged and packaged its Lua 5.4 modules under /usr/local/lib/lua/5.4, outside the default search paths. Set lua54path and lua54cpath to /usr/lib/lua/5.4 and update the package install rules to match. Bump PKG_RELEASE to 3 so the corrected package is offered as an upgrade. Keep Lua 5.1 and Lua 5.3 paths unchanged. Fixes: 3fe92e63f558 ("lua: look for lua5.4 modules under /usr instead of /usr/local") Signed-off-by: Jianhui Zhao

cqueues: fix Lua 5.4 module installation paths

2026-10-05T09:01:29Z

Commit 3fe92e63f558 moved the default Lua 5.4 module search paths from /usr/local to /usr. cqueues still staged and packaged its Lua 5.4 modules under /usr/local/lib/lua/5.4, outside the default search paths. Set lua54path and lua54cpath to /usr/lib/lua/5.4 and update the package install rules to match. Bump PKG_RELEASE to 3 so the corrected package is offered as an upgrade. Keep Lua 5.1 and Lua 5.3 paths unchanged. Fixes: 3fe92e63f558 ("lua: look for lua5.4 modules under /usr instead of /usr/local") Signed-off-by: Jianhui Zhao

lua-ffi: fix Lua 5.4 module installation path

2026-10-05T09:01:29Z

Commit 3fe92e63f558 ("lua: look for lua5.4 modules under /usr instead of /usr/local") changed LUA_ROOT to /usr/, moving the default Lua 5.4 module search paths out of /usr/local. The Lua 5.4 variant of lua-ffi still installed ffi.so under /usr/local/lib/lua/5.4, so require("ffi") could no longer find it with the default search paths. Install ffi.so under /usr/lib/lua/5.4 to match the new default search path. Bump PKG_RELEASE to 2 so the corrected package is offered as an upgrade. Keep the Lua 5.1 and Lua 5.3 installation paths unchanged. Fixes: 3fe92e63f558 ("lua: look for lua5.4 modules under /usr instead of /usr/local") Signed-off-by: Jianhui Zhao

lua-cjson: fix Lua 5.4 module installation path

2026-10-05T09:01:29Z

Commit 3fe92e63f558 ("lua: look for lua5.4 modules under /usr instead of /usr/local") changed LUA_ROOT to /usr/, moving the default Lua 5.4 module search paths out of /usr/local. The Lua 5.4 variant of lua-cjson still installed cjson.so under /usr/local/lib/lua/5.4, so require("cjson") could no longer find it with the default search paths. Install cjson.so under /usr/lib/lua/5.4 to match the new default search path. Bump PKG_RELEASE to 6 so the corrected package is offered as an upgrade. Keep the Lua 5.1 and Lua 5.3 installation paths unchanged. Fixes: 3fe92e63f558 ("lua: look for lua5.4 modules under /usr instead of /usr/local") Signed-off-by: Jianhui Zhao

lua-eco: align module installation with Lua 5.4 search paths

2026-10-05T09:01:29Z

Commit 3fe92e63f558 ("lua: look for lua5.4 modules under /usr instead of /usr/local") changed LUA_ROOT to /usr/, moving the default Lua 5.4 module search paths out of /usr/local. lua-eco still installed its Lua and native modules under /usr/local/lib/lua/5.4, so require() could no longer find them with the default search paths. Install modules from the main package and all subpackages under /usr/lib/lua/5.4, which is searched for both .lua and .so files. Define LUA_INSTALL_DIR once and use it throughout the install rules so future directory changes only need one update. Bump PKG_RELEASE to 2 so the corrected packages are offered as upgrades. Fixes: 3fe92e63f558 ("lua: look for lua5.4 modules under /usr instead of /usr/local") Signed-off-by: Jianhui Zhao

luasql: update to 2.7.0

2026-09-08T07:52:20Z

Refresh PKG_HASH from the tag tarball. Upstream moved from keplerproject to lunarmodules and the 2.7.0 tag has no leading v; point PKG_SOURCE_URL and the homepage URL at lunarmodules. Signed-off-by: Alexandru Ardelean

luajit2: update to 2026-07-31

2026-08-15T10:26:13Z

Also refresh 020-riscv64-support.patch from the current state of openresty/luajit2#236. The previous snapshot defined asm_tail_prep(ASMState *as), but since openresty/luajit2 commit 68354f44 the callers pass a second TraceNo argument, so the riscv64 build failed with: lj_asm.c:2559:5: error: too many arguments to function 'asm_tail_prep' The refreshed patch carries the upstream adaptation and restores the build. The other four patches apply unchanged. Signed-off-by: Josef Schlehofer