X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@mail.alpinelinux.org
Received: from dal-a2.localdomain (unknown [74.117.189.115])
	by mail.alpinelinux.org (Postfix) with ESMTP id 0BA21DC00AE
	for <alpine-devel@lists.alpinelinux.org>; Fri,  3 Jan 2014 07:23:29 +0000 (UTC)
Received: from ncopa-desktop.alpinelinux.org (3.203.202.84.customer.cdi.no [84.202.203.3])
	(using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	(Authenticated sender: ncopa@tanael.org)
	by dal-a2.localdomain (Postfix) with ESMTPSA id 28706BC1219;
	Fri,  3 Jan 2014 07:23:28 +0000 (UTC)
Date: Fri, 3 Jan 2014 08:23:24 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: Ted Trask <ttrask01@yahoo.com>
Cc: "alpine-devel@lists.alpinelinux.org"
 <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Avoiding bloat for Lua 5.1/5.2 modules
Message-ID: <20140103082324.7e5d3167@ncopa-desktop.alpinelinux.org>
In-Reply-To: <1388690847.16371.YahooMailNeo@web162801.mail.bf1.yahoo.com>
References: <20131231120758.50b5d559@ncopa-desktop.alpinelinux.org>
	<1388690847.16371.YahooMailNeo@web162801.mail.bf1.yahoo.com>
X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.20; x86_64-alpine-linux-uclibc)
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 2 Jan 2014 11:27:27 -0800 (PST)
Ted Trask <ttrask01@yahoo.com> 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].

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...)

-nc

[1] https://github.com/xlq/lua-subprocess/issues/2



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