Mail archive

Re: [alpine-devel] Avoiding bloat for Lua 5.1/5.2 modules

From: Ted Trask <>
Date: Mon, 19 Jan 2015 16:57:20 +0000 (UTC)

Now that Lua 5.3 is officially released, I just finished upgrading ACF to work with Lua 5.2. :/
Mostly I updated a bunch of packages to create and depend on subpackages for Lua 5.1 and Lua 5.2 support. This included some minor code updates. The most difficult change was forking lua-subprocess to properly support Lua 5.1 and Lua 5.2. The most significant change for Alpine Linux was to modify the haserl package. Two subpackages were created to install separate haserl binaries with Lua 5.1 and 5.2 support. The /usr/bin/haserl file is now a symlink to haserl-lua5.2. Since ACF is based upon haserl, installs based upon edge will now use Lua 5.2 for ACF. The change to haserl could present backward compatibility issues with other haserl scripts and should be noted in the release notes for Alpine Linux 3.2.
Please test and let me know if you find any problems.
PS. Wow, just realized while writing this email that the thread is over a year old. :(
PPS. ACF is no longer blocking the official switch from Lua 5.1 to Lua 5.2. So, we can possibly move toward making Lua 5.2 the default on Alpine Linux 3.2.
PPPS. If you're wondering about Lua 5.3 support, the current blocker is haserl, which doesn't build with Lua 5.3.
      From: Ted Trask <>
 To: Natanael Copa <>
Cc: "" <>
 Sent: Friday, January 3, 2014 9:07 AM
 Subject: Re: [alpine-devel] Avoiding bloat for Lua 5.1/5.2 modules
lua-subprocess was used to replace io.popen calls. Barthalion started to fork the project ( ) for 5.2 support, but did not finish. Right now, lua-subprocess is only referenced from 6 files because the vast majority of calls are done through a helper library. So, if we cannot get lua-subprocess to work with Lua 5.2, we could try replacing it with another package. I have never had the time to investigate writing lua libraries in C, so finishing the fork would take some time for me. Any other suggestions?

On Jan 3, 2014, at 2:23 AM, Natanael Copa <> wrote:

On Thu, 2 Jan 2014 11:27:27 -0800 (PST)
Ted Trask <> wrote:

Is there anything besides ACF that is preventing the wholesale move to Lua 5.2? My goal is to get ACF working with Lua 5.2 before the next release.

not really.

The stopper atm is lua-process i think, which seems abandoned from

I had a short look at it 2 months ago but there was use of environments
etc so I think it will need some refactoring to support 5.2.

If we could get rid of Lua 5.1 within close future, then we could
likely ship both 5.1 and 5.2 in the same lua-<module> package. (and
then we'll get lua 5.3...)



Received on Mon Jan 19 2015 - 16:57:20 UTC