> I've actually had a play with what I suggested above, sort of: in ~/lua I > have symlinks to the appropriate parts of the modules that would otherwise > be "luarocks make"d (at the moment these are all pure Lua so no building > is needed) and I've added that to LUA_PATH. It feels a bit hacky, but it > scratches the itch.
Not hacky at all, dev setup is different than production setup, so this is a good way to override settings in a dev setup. Probably most solid when scripted. This is exactly why Busted [1] for example has the --lpath and --cpath commandline options Thijs [1] http://olivinelabs.com/busted/#usage ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
