Nice work on this, thanks for the effort packaging. As the upstream on this it does feel like there are a few things we could refine to make downstream packaging easier. I'll commend on that in the issue you already opened. Two notes about this packaging...o

1. As I understand it this is not built against LuaJIT at all. That being the case, I think lua51-compat53 needs to be marked as Requires as well as BuildRequires. It is used at build time for some Lua C modules, so it's always needed at build time, you have that. At run time it is used to shim some functions in the Lua VM for Lua 5.1 and 5.2. Lua 5.3+ or LuaJIT don't need shimming (the latter including the shims we need anyway). But if this is really using Lua 5.1, it does need the runtime shimming too.

2. I assume the plan here is to fix the luajit package to include headers so that this can be eventually switched to that, correct? You could also get this to build with LuaJIT even without the system providing headers using --without-system-lua-sources, but I also understand that brings you to the trouble with offline builds. If there is anything I can do to fix that upstream let me know, I'm happy to make it possible for folks to get the 2× speed benefit of LuaJIT.

Both those points might be moot if I'm misunderstanding CARGO_FEATURE_VENDORED=1. Is that being used here to trick the configure phase into thinking it's using local Lua sources and then actually not doing that at build time?