Re: [gentoo-dev] [RFC] luajit global useflag
On Sun, Mar 1, 2015 at 6:46 PM, Rafael Goncalves Martins wrote: > On Sun, Mar 1, 2015 at 9:45 AM, Vadim A. Misbakh-Soloviov > wrote: >> В письме от Вс, 1 марта 2015 20:36:03 пользователь Ben de Groot написал: >>> >>> Or maybe one of the other lua package maintainers has plans? >> >> >> Not that I'm in-tree lua maintainer, but as Lua-overlay contributor and lua- >> fanboy, I'd suggest to unmask all lua-interpreters and make them slotted just >> as python/ruby/whatever. And provide a eselect-lua (I had ebuild for it >> somewhere). > > This isn't going to happen any time soon, for several reasons. :( > >> Although, there is single issue: precompiled bytecode isn't compatible >> between >> even "5.1" PUC-Rio Lua and LuaJIT, and, of course, AFAIR, between Lua5 >> releases. > > You explained why yourself. This issue can be solved doing something > like what is done for python, compiling and installing bytecode for > each interpreter, but unless someone implements this perfectly, at > least luajit isn't going to be involved in such thing. > >> But I don't think Lua-users do not know about that, so I don't think it is a >> real problem. > > No, this is a real problem to implement multi-interpreter support. > They don't care about the issue because they don't care about > supporting other interpreters, or even multiple versions of Lua > installed in parallel. > > I'm going to repeat this once again: Lua was designed to be built > statically, then upstream don't cares about compatibility between > different versions and interpreters. Creating static libraries is > something that distributions want (and is generally the best > approach), but the upstream developers don't care about this at all. > That said, if you want to go that way, you are in your own, upstream > isn't going to care about your issues or make your life easier. s/Creating static libraries/Creating shared libraries/ obviously. :) []'s -- Rafael Goncalves Martins Gentoo Linux developer http://rafaelmartins.eng.br/
Re: [gentoo-dev] [RFC] luajit global useflag
On Sun, Mar 1, 2015 at 9:45 AM, Vadim A. Misbakh-Soloviov wrote: > В письме от Вс, 1 марта 2015 20:36:03 пользователь Ben de Groot написал: >> >> Or maybe one of the other lua package maintainers has plans? > > > Not that I'm in-tree lua maintainer, but as Lua-overlay contributor and lua- > fanboy, I'd suggest to unmask all lua-interpreters and make them slotted just > as python/ruby/whatever. And provide a eselect-lua (I had ebuild for it > somewhere). This isn't going to happen any time soon, for several reasons. :( > Although, there is single issue: precompiled bytecode isn't compatible between > even "5.1" PUC-Rio Lua and LuaJIT, and, of course, AFAIR, between Lua5 > releases. You explained why yourself. This issue can be solved doing something like what is done for python, compiling and installing bytecode for each interpreter, but unless someone implements this perfectly, at least luajit isn't going to be involved in such thing. > But I don't think Lua-users do not know about that, so I don't think it is a > real problem. No, this is a real problem to implement multi-interpreter support. They don't care about the issue because they don't care about supporting other interpreters, or even multiple versions of Lua installed in parallel. I'm going to repeat this once again: Lua was designed to be built statically, then upstream don't cares about compatibility between different versions and interpreters. Creating static libraries is something that distributions want (and is generally the best approach), but the upstream developers don't care about this at all. That said, if you want to go that way, you are in your own, upstream isn't going to care about your issues or make your life easier. []'s -- Rafael Goncalves Martins Gentoo Linux developer http://rafaelmartins.eng.br/
Re: [gentoo-dev] [RFC] luajit global useflag
В письме от Вс, 1 марта 2015 20:36:03 пользователь Ben de Groot написал: > > Or maybe one of the other lua package maintainers has plans? Not that I'm in-tree lua maintainer, but as Lua-overlay contributor and lua- fanboy, I'd suggest to unmask all lua-interpreters and make them slotted just as python/ruby/whatever. And provide a eselect-lua (I had ebuild for it somewhere). Although, there is single issue: precompiled bytecode isn't compatible between even "5.1" PUC-Rio Lua and LuaJIT, and, of course, AFAIR, between Lua5 releases. But I don't think Lua-users do not know about that, so I don't think it is a real problem. -- Best regards, mva signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] [RFC] luajit global useflag
On 26 February 2015 at 22:44, Michał Górny wrote: > > > Ben de Groot 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 dev-lang/luajit instead >>of dev-lang/lua > > 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
Re: [gentoo-dev] [RFC] luajit global useflag
Ben de Groot 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 dev-lang/luajit instead >of dev-lang/lua 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. -- Michał Górny
Re: [gentoo-dev] [RFC] luajit global useflag
On Thu, Feb 26, 2015 at 01:36:24PM +0800, Ben de Groot wrote: > Use the lua just-in-time compiler dev-lang/luajit instead > of dev-lang/lua Wouldn't that make them both exclusive each other? -- Nicolas Sebrecht
Re: [gentoo-dev] [RFC] luajit global useflag
В письме от Чт, 26 февраля 2015 13:36:24 пользователь Ben de Groot написал: > I propose we make luajit a global useflag, using the description from > media-sound/csound: > > Use the lua just-in-time compiler dev-lang/luajit instead > of dev-lang/lua Voting up! Although, I'd also propose lua.eclass and patch all ebuilds declaring Lua support to support building against LuaJIT as well (since they're fully compatible at runtime). -- Best regards, mva signature.asc Description: This is a digitally signed message part.
[gentoo-dev] [RFC] luajit global useflag
% 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 dev-lang/luajit instead of dev-lang/lua -- Cheers, Ben | yngwin Gentoo developer
