On Sat, May 7, 2011 at 5:38 AM, Alexander Gladysh <[email protected]> wrote: > On Tue, May 3, 2011 at 14:04, steve donovan <[email protected]> wrote: > >> 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. > > For what it is worth, here is a makeshift implementation of some of > mentioned "capturing and parsing output" stuff: > > https://github.com/lua-aplicado/lua-aplicado/blob/master/lua-aplicado/shell/luarocks.lua > > Alexander. > > P.S. Hisham, don't you think it is time to merge some of commits from > Steve's repo? Like machine-readable luarocks list?
My take on it was that it would be better to eventually have an API to interact with LuaRocks program-to-program than to "freeze" the outputs of the command-line in order to make them predictable to other scripts. On the other hand, however, consistent outputs and being pipe-friendly is indeed the Unix way so maybe having a consistent command-line flag for commands to produce script-friendly outputs is the best approach. -- -- Hisham http://hisham.hm/ _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
