This is necessary because the standard library which is distributed with
lumail (the lumail core configuration so to speak) is written for lua5.1
apparently.
The website states 5.1 or 5.2 or 5.3, but 5.2 fails because "loadstring"
was deprecated in lua 5.2.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Includes:
* Package gets a flag to use the debug build
* install phase installs all lua scripts from the package and makes
lumail find them
* global configuration which is shipped with the package can be
overridden, if desired
* parallel building enabled
Those version specs only exist to keep compat with python 3.3 which we
are not using anyway.
(cherry picked from commit 560b2bce6ce84628f97e242a3015201378a90eef)
Semi-automatic update. These checks were done:
- built on NixOS
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk -h` got 0 exit code
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk --help` got 0 exit code
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk help` got 0 exit code
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk -v` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk --version` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk version` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk -h` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk --help` and found version 3.7.7
- ran `/nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7/bin/taktuk help` and found version 3.7.7
- found 3.7.7 with grep in /nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7
- found 3.7.7 in filename of file in /nix/store/l4zd353icm418x6asy4123a3gcpy14cr-taktuk-3.7.7
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarpidl_rosmsg -h` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarpidl_rosmsg --help` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarpidl_rosmsg help` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarpserver --help` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarp help` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarp version` and found version 2.3.70.2
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarp-config --help` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarp-config --version` and found version 2.3.70.2
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarpdev -h` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarpdev --help` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarpdev help` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarpmanager-console --help` got 0 exit code
- ran `/nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2/bin/yarpdatadumper --help` got 0 exit code
- found 2.3.70.2 with grep in /nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2
- found 2.3.70.2 in filename of file in /nix/store/bp68k0rdxw13rxgy93lqlqmrmprz272g-yarp-2.3.70.2
