From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 15A03138334 for ; Tue, 26 Mar 2019 21:30:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4D539E090E; Tue, 26 Mar 2019 21:30:43 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 02C72E08F0 for ; Tue, 26 Mar 2019 21:30:42 +0000 (UTC) Received: from patrickm (unknown [100.42.98.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: chutzpah) by smtp.gentoo.org (Postfix) with ESMTPSA id 5FF43335D00; Tue, 26 Mar 2019 21:30:41 +0000 (UTC) Date: Tue, 26 Mar 2019 14:30:38 -0700 From: Patrick McLean To: "Robin H. Johnson" Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] the state of dev-lang/lua Message-ID: <20190326143038.62cdcb03@patrickm> In-Reply-To: References: <20190323212327.GA24656@linux1.home> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 0453a9e3-9755-4a0e-837d-8107b907017f X-Archives-Hash: 98977cd51428c1b8ec2801fad9a52eaa On Mon, 25 Mar 2019 04:23:08 +0000 "Robin H. Johnson" wrote: > On Sat, Mar 23, 2019 at 04:23:27PM -0500, William Hubbs wrote: > > Hi all, > > > > Soon I will be working on fixing up the state of dev-lang/lua, and > > there are a couple of things I want to mention. > > > > The first thing is liblua as a shared library. If you are using lua > > internally in a program, upstream strongly recommends not linking it > > this way; it is supposed to be statically linked into the > > executable. Because of this, and because of the amount of custom > > patching we do to maintain liblua as a shared library, I plan to > > stop creating the shared library. > Please don't go back to static libraries. Look at the other major > distros, all of them shipped shared Lua as the primary method. +1 > > > I'm a bit undecided still about slotting lua. I'm sure we > > need subslots so we can force rebuilds when new lua releases enter > > the tree. However, I'm still unsure whether we need slots. I don't > > know of many things in the tree that are locked to a specific > > version of lua (there is only one package based on an irc > > conversation I had this week). > > Does anyone have any thoughts? > Lua needs first class slots, just like Python & Ruby, not just > subslots. Changing between versions can be a major undertaking. > > I think the slots to start with should be: > - lua5.1 > - lua5.2 > - lua5.3 > - luajit5.1 (this is basically an alternative implementation of > Lua5.1, much like pypy implements Python2). I think we are going to have to have slots for the "openresty" lua fork here as well. Several nginx modules require this version to work properly (I can provide more details if needed).