1 |
пн, 5 окт. 2020 г. в 22:20, Marek Szuba <marecki@g.o>: |
2 |
|
3 |
> > Is there a slotmove that can be applied? |
4 |
> |
5 |
> I am afraid I do not understand the question. What do you want to move, |
6 |
> and why? |
7 |
|
8 |
Currently portage is mostly lua:5.1 aware and the first thing is move |
9 |
dev-lang/lua:0 to 5.1 slot by slotmove in profiles/updates: |
10 |
|
11 |
slotmove dev-lang/lua 0 5.1 |
12 |
|
13 |
and update all ebuilds with dev-lang/lua:0 dependency (there are about |
14 |
200 ebuilds with that dependency, maybe there need to be an issue news |
15 |
item, since there may need to rebuild all dependencies). |
16 |
After that we need to unmask and stabilize "true" slotted lua:5.1 |
17 |
version, so this would be step 0 on slotted lua migration. After that |
18 |
migration of rest packages to new lua.eclass will be a lot easier. |
19 |
|
20 |
> > I think a better idea is to migrate the base set of lua packages |
21 |
> |
22 |
> Define "base set of lua packages". |
23 |
|
24 |
Well, core build ecosystem of lua packages: |
25 |
|
26 |
dev-lua/ldoc |
27 |
dev-lua/lpeg |
28 |
dev-lua/luacov |
29 |
dev-lua/luacrypto |
30 |
dev-lua/luadoc |
31 |
dev-lua/luarocks |
32 |
dev-lua/luasystem |
33 |
dev-lua/lua-utf8 |
34 |
dev-lua/lua-zlib |
35 |
|
36 |
maybe more. |
37 |
|
38 |
-- |
39 |
From Siberia with Love! |