1 |
[2019-03-23 16:23:27] William Hubbs: |
2 |
> The first thing is liblua as a shared library. If you are using lua |
3 |
> internally in a program, upstream strongly recommends not linking it |
4 |
> this way; it is supposed to be statically linked into the executable. |
5 |
> Because of this, and because of the amount of custom patching we do to |
6 |
> maintain liblua as a shared library, I plan to stop creating the shared |
7 |
> library. |
8 |
|
9 |
Pretty sure removing the shared version of liblua will cause a large |
10 |
amount of patching to be done in a lot of software that may not support |
11 |
static linking out of the box. |
12 |
|
13 |
> I'm a bit undecided still about slotting lua. I'm sure we |
14 |
> need subslots so we can force rebuilds when new lua releases enter the |
15 |
> tree. However, I'm still unsure whether we need slots. I don't know of |
16 |
> many things in the tree that are locked to a specific version |
17 |
> of lua (there is only one package based on an irc conversation I |
18 |
> had this week). |
19 |
> Does anyone have any thoughts? Are there more packages in the tree that |
20 |
> are locked to a specific version of lua? |
21 |
|
22 |
There should be slotting of lua, for example in the few programs that |
23 |
I know will need it: |
24 |
|
25 |
- app-editors/vis::{lua,lanodanOverlay}: Requires >=lua-5.2 |
26 |
does not support luajit (incomplete 5.2 compatibility) |
27 |
|
28 |
- media-video/mpv: requires lua:5.2 or luajit |
29 |
doesn’t seems to plan supporting 5.3[1] |
30 |
|
31 |
Also the lua overlay, which I would highly recommend using as a base |
32 |
has a slotted version of lua, instead of extending SLOT="0". |
33 |
|
34 |
1: https://github.com/mpv-player/mpv/wiki/FAQ#Why_does_mpv_not_support_Lua_53 |