| 1 |
On 2020-10-05 23:17, Azamat Hackimov wrote: |
| 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 |
The file structure of dev-lang/lua:0 differs from dev-lang/lua:5.x, |
| 14 |
meaning that introducing such a slot move would require Lua eclasses to |
| 15 |
treat lua5-1 differently from other targets. In other words, we would |
| 16 |
*still* need lua0 support but without a clearly distinct name. |
| 17 |
|
| 18 |
>> Define "base set of lua packages". |
| 19 |
> |
| 20 |
> Well, core build ecosystem of lua packages: |
| 21 |
> |
| 22 |
> dev-lua/ldoc |
| 23 |
> dev-lua/lpeg |
| 24 |
> dev-lua/luacov |
| 25 |
> dev-lua/luacrypto |
| 26 |
> dev-lua/luadoc |
| 27 |
> dev-lua/luarocks |
| 28 |
> dev-lua/luasystem |
| 29 |
> dev-lua/lua-utf8 |
| 30 |
> dev-lua/lua-zlib |
| 31 |
> |
| 32 |
> maybe more. |
| 33 |
|
| 34 |
And the advantage of having those migrated would be? It would make sense |
| 35 |
if these really were core to Lua support in other packages, like e.g. |
| 36 |
setuptools and the like in the Python world - but this varies wildly |
| 37 |
from package to package, with a large number of them depending on |
| 38 |
nothing but the Lua interpreter itself. |
| 39 |
|
| 40 |
-- |
| 41 |
MS |
Archives