On 2024-08-26 01:32, 'Kritzel Kratzel' via lua-l wrote:
> I am pleased to announce the new release of *OneLuaPro* v5.4.7.0:
>
https://github.com/OneLuaPro/OneLuaPro/releases <
https://github.com/OneLuaPro/OneLuaPro/releases>
> [...]
G'day, and thanks for your interesting release.
I'm on the other side of the fence... my "lglicua" Assistant, on
SourceForge, strives to bring Lua + LuaRocks + Selected Rocks
+ (optionally) Tecgraf's IM, CD and IUP packages to a number of
GNU/Linux distributions, especially Debian- (? Ubuntu-)based or
Red Hat-based.
https://sourceforge.net/projects/lglicua/files/
I have accommodation for multiple Lua versions, from 5.1 onwards,
and with a switching mechanism, so that not only Lua (and luac),
but also LuaRocks can be switched around (although LuaRocks'
dependence on environment variables usually results in a need to
reboot after a change, sigh).
Three minor observations:
1. I use 'std.normalize' to try to bring all Lua versions up to
a common denominator. In particular, I understand that Lua 5.1
is still quite popular, perhaps because of its LuaJIT overlap.
I personally use 5.1. as a lowest-common-denominator version
(without the deprecated "module" keyword, of course);
2. I always require 'std.strict', as this helps pick up typos
when creating scripts; and
3. I abhor using "io.popen", as it uses the system shell for all
sorts of things, which could lead to inappropriate command
mangling, which might, in turn, lead to security failures.
Instead, I include the Rock LuaPOSIX, and have my own
"pseudo-rock". PosixExec.lua. Command parameters are presented
as an array of strings in a table, with no interpretation
whatsoever.
You may find some of these Rocks valuable to include in your
package:
std.normalize;
std.strict;
luaposix; and
PosixExec.lua
In reverse, I'll look at the Rocks that you choose to bundle,
and may add some of them to my LuaRocks installer step.
Best wishes,
sur-behoffski (Brenton Hoff)
programmer, Grouse Software