On 2020-10-05 20:30, Azamat Hackimov wrote: > Is there a slotmove that can be applied?
I am afraid I do not understand the question. What do you want to move, and why? > Can be lua:0 and lua:5.1 coexist? In theory they can (I say "in theory" because app-eselect/eselect-lua ebuild currently block dev-lang/lua:0), except having :0 installed would conflict with using eselect-lua - which I guess might be acceptable during the transition period. Anyway, there are no file collisions between :0 and :5.1, and while the two use the same CMOD and LMOD directories (for the record, so does LuaJIT for now) this should be harmless - files in LMOD would be very much identical, and from what I recall from discussions on IRC compiled modules in CMOD must not link against Lua libraries themselves so they should be implementation-independent. > I think a better idea is to migrate the base set of lua packages Define "base set of lua packages". > (maybe under package.mask) ...meaning that at some point in the future we would have to unmask slotted Lua AND all the ebuilds depending on it, potentially unleashing a torrent of errors. Although we cannot really avoid this step altogether, I would rather let maintainers adapt their Lua ebuilds to the eclasses first and handle slotted Lua as a separate step. -- MS
signature.asc
Description: OpenPGP digital signature
