> This variable is set by default to be name of the interpreter, but it > is meant to be a $(LUA) variable accessible to rockspecs in the same > way that $(CC) is. Setting LUA with a full path in a configuration > file shouldn't break things. LuaRocks uses LUA_INTERPRETER internally > -- set in site_config.lua -- when it wants only the interpreter name > (for example, see luarocks/fs/unix.lua).
It might make sense to define its meaning clearly one way or another, though, no? Otherwise, even if LuaRocks does not use it internally, there is a risk of different rocks making different assumptions, some assuming LUA to contain a full path while others assuming its just the name and thus prepending $LUA_BINDIR to get the full path. It would then become necessary to change the config file between installing different rocks, which sounds undesirable. - yuri ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
