On Fri, Aug 5, 2011 at 9:39 AM, steve donovan <[email protected]> wrote: > On Fri, Aug 5, 2011 at 9:31 AM, Jim Whitehead II <[email protected]> wrote: >> That's all I'm doing by directly editing luaconf.h, forcing that to >> always be the case so I can truly say that out of the box the lua >> executable only looks at the sandbox path to get modules. I'm not sure >> why that's objectionable.. > > It's certainly how Lua is intended to be used. Given how easy it is to > rebuild, I can't see the problem either. > > With the Lua for Linux experiments, I felt no guilt whatsoever in > patching Lua so that it could run locally. The idea then was that > people could 'try before they buy' and have the convenience of a > distribution that sits in its own self-contained directory.
I think its about time I point out that LuaDist basically does what this whole thread is about. The Lua[1] distributed with LuaDist has small patch applied (optional) so that LUA_CPATH and LUA_PATH can use the "!/path/to/modules" notation for relative deployment of modules on platforms other than Windows. Additionally it uses rpath on linux making it self contained without need to set up any environment. Sadly I have not yet patched LuaRocks to work with it correctly, however the modules you might be interested in probably are in the LuaDist Repository[2]. pd [1] https://github.com/LuaDist/lua [2] https://github.com/LuaDist/Repository ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
