When I use "require 'luarocks.loader'" in my ~/.luarc (loaded by
LUA_INIT), I find that it changes package.path and package.cpath by
prepending the relevant library directories, e.g. lib_dir. This causes
problems with test suites which want to test a just-built version of a
module, and prepend the build directory to path/cpath, only to find
that it has been overridden in favour of installed modules by
luarocks.
Since according to the luarocks documentation, you should in any case
change your default LUA_PATH/LUA_CPATH to point to the directories in
which LuaRocks installs modules (if necessary), should LuaRocks really
be changing the paths itself? Just from a tidyness point of view, this
means that the paths LuaRocks uses are duplicated in my
package.{c,}path.
Note that I do want to be able to use LuaRocks (including,
potentially, multiple version support, hence luarocks.loader) when
building and testing programs, so simply omitting LuaRocks causes
another problem.
--
http://rrt.sc3d.org
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Luarocks-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
