Hi all, Although much information can be extracted by capturing and parsing the output of various LuaRocks commands such as search, list, show, etc it would sometimes be very convenient if a Lua application could query LuaRocks directly. Then it would be straightforward to build custom tools to manage LR directly.
I'm not (at this point) thinking about something that is directly part of LR, rather something that can be itself delivered as a rock. That would speed up development and testing without having to interfere with LR's release schedule. Now before I wander off and knock something together, the question is: what information should be exposed? Initially I was thinking of exposing the information returned by the 'show' command. A use case for this: - if an application wants to ship extra information, data, etc with a rock; this API would allow it to find that stuff in the rocks tree. For instance, my Orbiter framework relies on modules being able to find their resources (images, style sheets, etc). Currently it naively assumes that the resources directory is bundled in the same directory as the module, which isn't a good idea in general. (BTW, if there is an existing mechanism for doing this in LR I'd be happy to know about it) steve d. _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
