1 |
On Sat, 2019-03-23 at 16:23 -0500, William Hubbs wrote: |
2 |
> Hi all, |
3 |
> |
4 |
> Soon I will be working on fixing up the state of dev-lang/lua, and there |
5 |
> are a couple of things I want to mention. |
6 |
> |
7 |
> The first thing is liblua as a shared library. If you are using lua |
8 |
> internally in a program, upstream strongly recommends not linking it |
9 |
> this way; it is supposed to be statically linked into the executable. |
10 |
> Because of this, and because of the amount of custom patching we do to |
11 |
> maintain liblua as a shared library, I plan to stop creating the shared |
12 |
> library. |
13 |
|
14 |
You mean the ~8 lines used to create shared objects and library? Sure, |
15 |
it really makes sense to turn Gentoo into security/minor rebuild |
16 |
nightmare just to please upstream's wannabe/laziness. |
17 |
|
18 |
I suppose you realize that >50% of that patch is actually about |
19 |
slotting, right? |
20 |
|
21 |
> I'm a bit undecided still about slotting lua. I'm sure we |
22 |
> need subslots so we can force rebuilds when new lua releases enter the |
23 |
> tree. However, I'm still unsure whether we need slots. I don't know of |
24 |
> many things in the tree that are locked to a specific version |
25 |
> of lua (there is only one package based on an irc conversation I |
26 |
> had this week). |
27 |
> Does anyone have any thoughts? Are there more packages in the tree that |
28 |
> are locked to a specific version of lua? |
29 |
> |
30 |
|
31 |
You won't know that, given that there's only a single unmasked version, |
32 |
so not many people have tested the new versions. You could create |
33 |
unslotted, masked 5.3 ebuild and ask Toralf to give it a ride. |
34 |
|
35 |
-- |
36 |
Best regards, |
37 |
Michał Górny |