On Tue, Dec 24, 2013 at 1:34 AM, Alexander Gladysh <aglad...@gmail.com> wrote: > Hi, list! > > Many our rocks come with a generated list of exported symbols. > > For example: > https://github.com/lua-nucleo/lua-nucleo/blob/master/lua-nucleo/code/exports.lua > > I'm writing a code analysis tool, and would like to get a list of all > files code/exports.lua that are installed via LuaRocks, in the form > that is package.path-aware. > > I.e. if I've installed lua-nucleo and lua-aplicado rocks on my box, > I'd like to have a list: > > { > "lua-nucleo/code/exports.lua"; > "lua-aplicado/code/exports.lua"; > } > > Is there a better way to do that than this ugly and convoluted command > that tries to overcome machine-unfriendliness of LuaRocks output? > > $ luarocks list | grep '^[^ ]' | tail -n +4 | xargs -n1 luarocks show > | grep code.exports > > This command takes five seconds to execute on my box with 74 rocks > installed. This is way to slow for my tool. :-(
To compare, this hack takes 0.2s: $ (cd `luarocks path | grep LUA_PATH | cut -d "'" -f 2- | cut -d "?" -f 1` && find . -wholename '*code/exports.lua' | cut -c 3-) Alexander. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
