On 26 February 2015 at 22:44, Michał Górny <mgo...@gentoo.org> wrote:
>
>
> Ben de Groot <yng...@gentoo.org> napisał:
>
>> % quse -D luajit
>>local:luajit:app-editors/gvim: Use dev-lang/luajit instead of
>>dev-lang/lua
>>local:luajit:app-editors/vim: Use dev-lang/luajit instead of
>>dev-lang/lua
>>local:luajit:app-editors/vim-qt: Use dev-lang/luajit instead of
>>dev-lang/lua
>>local:luajit:games-action/minetest: Use dev-lang/luajit instead of
>>dev-lang/lua
>> local:luajit:games-engines/solarus: Use LuaJIT instead of default Lua.
>> local:luajit:games-roguelike/stone-soup: Use dev-lang/luajit as
>>scripting backend instead of dev-lang/lua.
>> local:luajit:media-sound/csound: Use the lua just-in-time compiler
>>dev-lang/luajit instead of dev-lang/lua
>>local:luajit:media-video/mpv: Use dev-lang/luajit instead of
>>dev-lang/lua
>> local:luajit:www-client/luakit: Use the lua just-in-time compiler
>>dev-lang/luajit instead of dev-lang/lua, which should make luakit
>>faster.
>> local:luajit:www-servers/nginx: Use dev-lang/luajit instead of
>>dev-lang/lua for lua support when building the lua http module.
>>
>>I propose we make luajit a global useflag, using the description from
>>media-sound/csound:
>>
>>Use the lua just-in-time compiler <pkg>dev-lang/luajit</pkg> instead
>>of <pkg>dev-lang/lua</pkg>
>
> How about we figure out how to handle multiple versions and interpreters 
> sanely instead? Not that I mind USE=luajit but I do mind the huge 
> conditionals with random USE flags like recently suggested for neovim.
>

That would be great going forward. But at this point it's a non-issue.
There is a choice between lua-5.1 and luajit. Other lua versions have
been masked since like forever. And I don't see that situation
changing anytime soon.

Or maybe one of the other lua package maintainers has plans?

-- 
Cheers,

Ben | yngwin
Gentoo developer

Reply via email to