Hi all,

Somewhat a newcomer to the Lua community, I am doing a Summer of Code
project on LuaRocks, the luarocks addon system. Basically, the system
will allow enable addons that can plug into the building process of
rocks and do basically arbitrary things. See the SoC ideas page [1] or
Hisham's talk [2] for more.

However, to make the life of addon developers easier as well as to
prevent the addons from destroying the world, we first have to define
an API for the addons to interact with luarocks internals. The API
would, of course, depend on what kind of addons we have in vision.
Hence I would like to have your suggestions on two questions:

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.

1. http://www.lua.inf.puc-rio.br/gsoc/ideas2015.html#luarocks
2. http://luaconf.ru/#Muhammad

-- 
Best regards,
肖骐 XIAO Qi

------------------------------------------------------------------------------
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

Reply via email to