X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from nm30-vm0.bullet.mail.bf1.yahoo.com (nm30-vm0.bullet.mail.bf1.yahoo.com [98.139.213.126]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id D0E47DC00F7 for ; Mon, 19 Jan 2015 17:02:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1421686953; bh=iQp6tbdE2E5auf9yFp2esbkL5ybn2Ip5R0843EPOfn8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=VgU7qfaMetm6n4p046InX/uL+1uTMOzp5ddLJKaPJXvBMO1Qivq0NFSCVYBP9K4wvSKdok5irxRuQ3fnTM+aCulIA3sraWYQ7ig0zlZ1AY/606RatnYhfR4NKHUOHTpjFgezh/rXHjHiiCd8pogzCRLXD1uTYr46nPT7mslHZB+CrSapPQLJGakYx0Thj2eViFZAmwjCX6rYVTHoE4d7zMiU+jPPtkcSAGNqufJnPW5SLpU/AwX71FhIzpc/ns9lrqGRL5T6+7szo0Xd/BGZbBS7RRsdmzaWVr9Un1gasyX+simlDY5fRS8kQsSBm1nzF8xIlGRZcMde1w0+poivEA== Received: from [98.139.212.151] by nm30.bullet.mail.bf1.yahoo.com with NNFMP; 19 Jan 2015 17:02:33 -0000 Received: from [98.139.212.247] by tm8.bullet.mail.bf1.yahoo.com with NNFMP; 19 Jan 2015 17:02:33 -0000 Received: from [127.0.0.1] by omp1056.mail.bf1.yahoo.com with NNFMP; 19 Jan 2015 16:57:21 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 845797.85319.bm@omp1056.mail.bf1.yahoo.com X-YMail-OSG: AnF7JTgVM1lrSBGon7_lLFMW4umEEerIsZDEjaDnAax4DoQyHoI7hGvrvxvCsDv qyNancTHh.n5Apt3yFKR8m8UM2DI7MJb.YYen1JHaM_rB4OzO1CtZFVcH9yB7gpWL6Yr80mvatTZ OrxHHPknGXtWk1kg.r4qdcWI0aex_ECgRMyzcGOLz86N2j9qOjMPKP2mRLIHLqEgYXz11Mz0BrWV gWq90GEtus1T0fFoxtytJn6nVauBf2Sr_E4P1tgPTuRIywaakxH8sV9lreLsYssEt0DVXaVif_Qf gOKzXgwTQMTrSmXgJeb3l3Zoe_HV1fEd96u4u7F9DoRT_l1XyHg9ac1MK83P_VbQaupf09dCM_2E y1R8C32WBiwG2t.x3eBjLTAi155JVrnSG9ywtzMvdo3c4jdDR7pmq6f2b1.ypDL_yYeqe7tNDT3r lQCTa7HHa45I5Ir6WrSNm1J22Q45bCS9gG68vfnibw9Md4bjxyyj8_yM2pgN80jZRxKrA9lJfEY3 Ff4zBDvorHILyFuE6xNMJNC2GOXw2c0xm.SjWbgEx3IjLBiSXqbgLi0aqpz84VrfuS9iyT6PECmo Kr0jILZjmAPjfAnnbFsvWABW.2ZhXRGrzPqePagAH Received: by 76.13.26.127; Mon, 19 Jan 2015 16:57:21 +0000 Date: Mon, 19 Jan 2015 16:57:20 +0000 (UTC) From: Ted Trask Reply-To: Ted Trask To: Natanael Copa Cc: "alpine-devel@lists.alpinelinux.org" Message-ID: <1969139959.3357802.1421686640893.JavaMail.yahoo@jws10603.mail.bf1.yahoo.com> In-Reply-To: <3F946EBD-63D3-4A12-A770-BBE41E5D8FBC@yahoo.com> References: <3F946EBD-63D3-4A12-A770-BBE41E5D8FBC@yahoo.com> Subject: Re: [alpine-devel] Avoiding bloat for Lua 5.1/5.2 modules X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3357801_63202251.1421686640883" ------=_Part_3357801_63202251.1421686640883 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Now that Lua 5.3 is officially released, I just finished upgrading ACF to w= ork with Lua 5.2. :/ Mostly I updated a bunch of packages to create and depend on subpackages fo= r Lua 5.1 and Lua 5.2 support. This included some minor code updates. The m= ost 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 th= e haserl package. Two subpackages were created to install separate haserl b= inaries with Lua 5.1 and 5.2 support. The /usr/bin/haserl file is now a sym= link 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 backw= ard compatibility issues with other haserl scripts and should be noted in t= he release notes for Alpine Linux 3.2. Please test and let me know if you find any problems. Ted PS. Wow, just realized while writing this email that the thread is over a y= ear 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 has= erl, which doesn't build with Lua 5.3. From: Ted Trask To: Natanael Copa =20 Cc: "alpine-devel@lists.alpinelinux.org" =20 Sent: Friday, January 3, 2014 9:07 AM Subject: Re: [alpine-devel] Avoiding bloat for Lua 5.1/5.2 modules =20 lua-subprocess was used to replace io.popen calls. Barthalion started to fo= rk the project (=C2=A0https://github.com/Barthalion/lua-subprocess ) 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 invest= igate writing lua libraries in C, so finishing the fork would take some tim= e for me. Any other suggestions? Ted 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 upstream[1]. l 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- package. (and then we'll get lua 5.3...) -nc [1] https://github.com/xlq/lua-subprocess/issues/2 --- Unsubscribe: =C2=A0alpine-devel+unsubscribe@lists.alpinelinux.org Help: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0alpine-devel+help@lis= ts.alpinelinux.org --- ------=_Part_3357801_63202251.1421686640883 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Now that Lua 5.3 is officially relea= sed, I just finished upgrading ACF to work with Lua 5.2. :/

Mostly I updated a bunch of pack= ages to create and depend on subpackages for Lua 5.1 and Lua 5.2 support. T= his 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 significa= nt change for Alpine Linux was to modify the haserl package. Two subpackage= s were created to install separate haserl binaries with Lua 5.1 and 5.2 sup= port. 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 AC= F. The change to haserl could present backward compatibility issues with ot= her haserl scripts and should be noted in the release notes for Alpine Linu= x 3.2.

<= /div>
Please test = and let me know if you find any problems.

Ted

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 Linu= x 3.2.

<= /div>
PPPS. If you= 're wondering about Lua 5.3 support, the current blocker is haserl, which d= oesn't build with Lua 5.3.

From: Ted Trask <ttrask01@yah= oo.com>
To: Natanae= l Copa <ncopa@alpinelinux.org>
Cc: "alpine-devel@lists.alpinelinux.org" <alpine-devel@li= sts.alpinelinux.org>
Sent: Friday, January 3, 2014 9:07 AM
Subject: Re: [alpine-devel] Avoiding bloat for Lua 5.1/5= .2 modules

l= ua-subprocess was used to replace io.popen calls. Barthalion started to for= k the project ( https://github.com/Bar= thalion/lua-subprocess ) 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-subpro= cess 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 fin= ishing the fork would take some time for me. Any other suggestions?<= br clear=3D"none">
Ted

On Jan 3, 2014, at 2:23 AM, Natanael Co= pa <ncopa@alpinelinux.org> wrote:

On Thu, 2 Jan 2014 11:27:27 -0= 800 (PST)
Ted Trask <ttr= ask01@yahoo.com> wrote:

Is there anything besid= es 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 abando= ned from
upstream[1].



l
I had a short look at it 2 months ago but there was use of environm= ents
etc so I think it will need some refact= oring 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 lu= a-<module> package. (and
then we'll ge= t lua 5.3...)

-nc

[1] https://github.com/xlq/lua-subprocess/issue= s/2




---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org

---



------=_Part_3357801_63202251.1421686640883-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---