Closed magnusviri closed 1 day ago
So, if i'm reading correctly, both lua should list luarocks as a companion, and both should have runtime variables pointing to the share directories. does it work properly with only the directory paths, and not the specific files listed as well?
export LUA_PATH="/opt/pkgx/lua.org/v\*/share/lua/5.4;/opt/pkgx/lua.org/v*/lib/lua/5.4;;/opt/pkgx/luarocks.org/v*/share/lua/5.4;/opt/pkgx/luarocks.org/v*/lib/lua/5.4"
export LUA_CPATH="/opt/pkgx/lua.org/v*/lib/lua/5.4/;/opt/pkgx/luarocks.org/v*/lib/lua/5.4"
nope, as always, your fix is perfect. ugly, but that's lua's fault. pr incoming with a test for your specific issue.
Ok, I feel dumb because there might be a better solution. Luarocks can specify an install directory like this: luarocks install --tree ~/.local/lua
. I'm not sure where you guys install stuff with gems and pip, but this is similar to that. That directory should probably be included in LUA_PATH and LUA_CPATH instead of the luarocks.org pkgx directory. I included the luarocks pkgx directory because that's where luarocks installs stuff by default.
ooh, good catch. looks like we might be using ~/.gems
if i'm reading the patches correctly. i wonder what's considered standard.
I'm trying to use luasockets.
This fixes it. I'm not sure how you want to integrate it. (see https://www.lua.org/manual/5.4/lua.html)