On Apr 3, 2013, at 5:21 AM, Gaspard Bucher <[email protected]> wrote: > Now I stumble on something I was really not expecting: what is the proper way > to test my modules against lua 5.2 ? > > Installing is OK (even if it overwrites /usr/local/bin/lua). Now I have three > binaries to test "lua", "lua5.2" and "luajit". The problem is ... luarocks.
You must launch luarocks with the same Lua interpreter than you plan to use with the installed rock. The least confusing approach is brute force: "make install" Lua 5.1, "luarocks install" the unit under test, test, "make install" Lua 5.2, "luarocks install" the unit under test, test, etc. This overwrites the stuff in /usr/local/lib and usr/local/bin on each Lua install to make luarocks and other tools happy. It looks like Debian based systems have a special set of directories for Lua 5.1 and Lua 5.2 binaries, and use symlinks in /usr/local/lib and usr/local/bin to select the default Lua. It seems like a nice approach, however, you then need to deal with possible differences between the configuration assumed by the Debian packages versus the upstream libraries and their luarocks files. e ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
