Re: [gentoo-dev] the state of dev-lang/lua

["Michał Górny" <mgorny@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

On Sat, 2019-03-23 at 16:23 -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.

You mean the ~8 lines used to create shared objects and library?  Sure,
it really makes sense to turn Gentoo into security/minor rebuild
nightmare just to please upstream's wannabe/laziness.

I suppose you realize that >50% of that patch is actually about
slotting, right?

> 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?
> 

You won't know that, given that there's only a single unmasked version,
so not many people have tested the new versions.  You could create
unslotted, masked 5.3 ebuild and ask Toralf to give it a ride.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]