Hi! > On 26 May 2015, at 01:39, Philipp Janda <siffie...@gmx.net> wrote: > > Am 26.05.2015 um 00:47 schröbte XIAO Qi: >> Hi all, > > Hi! > >> >> 1) As a rock developer, what kind of addons would you like to have? >> >> 2) As a prospective addon developer, which parts of LuaRocks should be >> available to plug into? >> >> As an example, say as a rock developer, I wish to have addons that do >> testing after building the rock. And in turn, as a prospective >> developer for the testing addon, I would like to have the list of >> modules available to the addon (in the case of the "builtin" backend), >> and would like to report test failures and possibly prevent the rock >> from installing. > > You already mentioned unit tests (or system tests), and I see that the > GSoC page also lists automatic documentation generation using tools like > LDoc, lut, Docco, Doxygen, naturaldocs, etc. Those two are the important > ones for me, but I'll throw in another idea: There are some source to > source transformation tools (e.g. LuaMacro, Moonscript, Objective Lua, > MetaLua, some amalgamation tools, or even plain luac). It would be nice > to be able to transform at build time and install the precompiled files > instead of the original source code. Of course there are also some > programming languages that generate C code as output (but I don't care > much about those) ... > > Also I'd like the option of skipping any unit tests (and installing the > unit testing framework in the first place) using a configuration > variable or a command line flag. So we probably need a command line > option and config variable namespace for addons. > > Philipp
I use help2man for generating basic manual pages for my Lua packages, and have a long standing TODO item to teach luarocks how to: 1. Install the manual pages idiomatically, e.g. .../man/man1/specl.1 2. Have eval `luarocks path` know how to set MANPATH appropriately If there was a more general way to allow that so that a simple add on could do this work, that would be awesome! I second the idea about unit tests. As the author of Specl, I'd love to be able to hook a unit-test capability into my rocks without passing a shared bunch of automake gunk around my projects. The final think I have dreamed about is a more extensible build system in LuaRocks. While the built in mechanism is great for basic Lua-only rocks, it falls short on installing non-Lua files (e.g. data, configuration, manual pages), and especially the kinds of host environment tests needed for C language rocks that mean luaposix and the like have almost no option but to use Autotools. Cheers, -- Gary V. Vaughan (gary AT vaughan DOT pe) ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
