| 1 |
On 12/7/20 9:11 AM, Marek Szuba wrote: |
| 2 |
> On 2020-12-04 13:16, Marek Szuba wrote: |
| 3 |
> |
| 4 |
>> Since a week ago the number of open bugs blocking the slotted-Lua |
| 5 |
>> tracker has been reduced from 119 to under 80. |
| 6 |
> |
| 7 |
> Updated count as of a few minutes ago: 64 open tickets! Full list: |
| 8 |
> |
| 9 |
> https://dev.gentoo.org/~marecki/open_blocking_lua_eclass_bugs-20201207135752.txt |
| 10 |
> |
| 11 |
|
| 12 |
I think the slotted lua ebuilds should be doing some eselect-lua stuff |
| 13 |
in pkg_postinst() and pkg_postrm(). For example: |
| 14 |
|
| 15 |
* I have lua-5.1 and lua-5.2 installed |
| 16 |
* Lua-5.2 is eselected |
| 17 |
* I uninstall lua-5.2 |
| 18 |
* Now /usr/lib64/pkgconfig/lua.pc is a dangling symlink |
| 19 |
|
| 20 |
Related to the above: is there a way to trigger rebuilds of consumers |
| 21 |
when the "single implementation" changes? If I have a package that links |
| 22 |
against liblua and if I upgrade from lua-5.1 to lua-5.2, then my package |
| 23 |
should rebuild. I don't think $LUA_DEPS from lua-single.eclass can do that? |
Archives