On Thu, 2020-09-03 at 15:37 +0200, Marek Szuba wrote: > Ladies and gentlemen, > > Here is my first attempt on creating an eclass which would handle > installation of Lua modules for multiple implementations. As some of > you > are aware of, the lack of such an eclass has been a major issue for > our > efforts on slotting dev-lang/lua. > > With many, many thanks to mgorny and everyone else who has worked on > python-r1.eclass, to whom lua.eclass bears, ahem, striking > resemblance. > > At the moment this is only really useful for installing Lua modules > but > assuming it doesn't turn out to be a total failure, I'll work on > single-target support as the next step. We should probably think about > adding LuaJIT support at some point too. > > Comments are very much welcome!
This is finally going in the right direction. Unfortunately we won't get around a single-r1-style eclass too. What about all those programs embedding a specific lua version as plugin architecture? Conversely, we also won't get around the multi eclass too, given how many upstreams won't unbundle/port their lua dependencies and require access to pure- lua packages. But the basic principles underlying your eclass are finally correct, unlike the previous lua.eclass attempt.
