From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-86840-garchives=archives.gentoo.org@lists.gentoo.org>
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 3E185138334
	for <garchives@archives.gentoo.org>; Sun, 24 Mar 2019 11:24:33 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id AB117E099E;
	Sun, 24 Mar 2019 11:24:29 +0000 (UTC)
Received: from cloudsdale.the-delta.net.eu.org (cloudsdale.the-delta.net.eu.org [IPv6:2a01:4f8:1c17:4b6d::1])
	(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 1A4A9E0995
	for <gentoo-dev@lists.gentoo.org>; Sun, 24 Mar 2019 11:24:28 +0000 (UTC)
Received: from localhost (cloudsdale.the-delta.net.eu.org [local])
	by cloudsdale.the-delta.net.eu.org (OpenSMTPD) with ESMTPA id 5048a474
	for <gentoo-dev@lists.gentoo.org>;
	Sun, 24 Mar 2019 11:24:26 +0000 (UTC)
Date: Sun, 24 Mar 2019 12:24:26 +0100
From: contact@hacktivis.me
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] the state of dev-lang/lua
Message-ID: <20190324112426.GD30037@cloudsdale.the-delta.net.eu.org>
References: <20190323212327.GA24656@linux1.home>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
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=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20190323212327.GA24656@linux1.home>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Archives-Salt: 8b163a47-18c4-4bea-b63a-a448aad5ca22
X-Archives-Hash: 2a382a6c1694c8f565586c3d3c6f329a

[2019-03-23 16:23:27] William Hubbs:
> 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.

Pretty sure removing the shared version of liblua will cause a large
amount of patching to be done in a lot of software that may not support
static linking out of the box.

> 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? Are there more packages in the tree that
> are locked to a specific version of lua?

There should be slotting of lua, for example in the few programs that
I know will need it:

- app-editors/vis::{lua,lanodanOverlay}: Requires >=lua-5.2
	does not support luajit (incomplete 5.2 compatibility)

- media-video/mpv: requires lua:5.2 or luajit
	doesn’t seems to plan supporting 5.3[1]

Also the lua overlay, which I would highly recommend using as a base
has a slotted version of lua, instead of extending SLOT="0".

1: https://github.com/mpv-player/mpv/wiki/FAQ#Why_does_mpv_not_support_Lua_53