Hi, > The first (and in my mind most important) is a standard test step. As > far as I can tell, luarocks supports only build and install phases. I've > ...
A testing phase when building stuff with luarocks may be useful. I usually have a bunch of tests with my modules (OK, with 2 relased m,odules, "usually" might be too strong a word ;) ), and it might be useful for the module author to have to run and pass a test suite of sorts in order for an installation to succeed. However, I would prefer this to be a single test file that exits with success or failure. > The second step (which Perl's packaging provides) is automatic generation > and installation of documentation. I've been out of the Lua world for a Not too sure about the generation. A unified access to documentation would be nice, aka perldoc, but I feel that something like the recently discussed info command for luarocks would be sufficient, i.e. have luarocks point you at the docs. I handle documentation generation from the skript that packs my rocks for me, this works quite well. Gunnar _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
