On Fri, Sep 3, 2010 at 5:12 PM, Hisham <[email protected]> wrote: > just like LuaRocks 1 did. It moves modules out of the rock directory > and into the common module path (e.g. /usr/local/share/lua/5.1 and > /usr/local/lib/lua/5.1) after "make install".
Right, that makes sense, thanks... > mind I can review rockspecs but I can't actually run and install them > all, due to external dependencies. Of course, no single tree is going to be able to have both LuaCOM and lposix installed! > Perhaps we come up with a way to make it easy for contributors to > share the rockspec they wrote plus the automatically generated > rock_manifest file for their rock. That is exactly the kind of information one would need on the server side - maybe we would end up with something like luaexpat-1.1.0-4.manifest; if LR needed that information it could download this file, and if this failed it would not be a disaster. (It would be fairly easy to add this as yet another option to the show command: 'copy the rock_manifest here and give it a suitable name'. That may be stretching the meaning of the word 'show' however..) steve d. _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
