1 |
On Mon, 25 Mar 2019 04:23:08 +0000 |
2 |
"Robin H. Johnson" <robbat2@g.o> wrote: |
3 |
|
4 |
> On Sat, Mar 23, 2019 at 04:23:27PM -0500, William Hubbs wrote: |
5 |
> > Hi all, |
6 |
> > |
7 |
> > Soon I will be working on fixing up the state of dev-lang/lua, and |
8 |
> > there are a couple of things I want to mention. |
9 |
> > |
10 |
> > The first thing is liblua as a shared library. If you are using lua |
11 |
> > internally in a program, upstream strongly recommends not linking it |
12 |
> > this way; it is supposed to be statically linked into the |
13 |
> > executable. Because of this, and because of the amount of custom |
14 |
> > patching we do to maintain liblua as a shared library, I plan to |
15 |
> > stop creating the shared library. |
16 |
> Please don't go back to static libraries. Look at the other major |
17 |
> distros, all of them shipped shared Lua as the primary method. |
18 |
|
19 |
+1 |
20 |
|
21 |
> |
22 |
> > I'm a bit undecided still about slotting lua. I'm sure we |
23 |
> > need subslots so we can force rebuilds when new lua releases enter |
24 |
> > the tree. However, I'm still unsure whether we need slots. I don't |
25 |
> > know of many things in the tree that are locked to a specific |
26 |
> > version of lua (there is only one package based on an irc |
27 |
> > conversation I had this week). |
28 |
> > Does anyone have any thoughts? |
29 |
> Lua needs first class slots, just like Python & Ruby, not just |
30 |
> subslots. Changing between versions can be a major undertaking. |
31 |
> |
32 |
> I think the slots to start with should be: |
33 |
> - lua5.1 |
34 |
> - lua5.2 |
35 |
> - lua5.3 |
36 |
> - luajit5.1 (this is basically an alternative implementation of |
37 |
> Lua5.1, much like pypy implements Python2). |
38 |
|
39 |
I think we are going to have to have slots for the "openresty" lua |
40 |
fork here as well. Several nginx modules require this version to work |
41 |
properly (I can provide more details if needed). |