On Tue, Dec 21, 2010 at 21:32, Hisham <[email protected]> wrote: > On Tue, Dec 21, 2010 at 8:42 PM, Alexander Gladysh <[email protected]> wrote: >> On Wed, Dec 22, 2010 at 01:26, Hisham <[email protected]> wrote: >>> On Tue, Dec 21, 2010 at 11:45 AM, steve donovan >>> <[email protected]> wrote: >>>> On Tue, Dec 21, 2010 at 3:14 PM, Hisham <[email protected]> wrote: >> >>> Sure, that would be great. However, I can't commit myself to actually >>> _run_ the rockspecs we receive. I often do so when the rockspec has no >>> external dependencies (and sometimes even when it does) to make sure >>> it builds well when something catches my eye. Rockspecs already take >>> too long sometimes to be uploaded (and I thank Fabio for helping me >>> out on this whenever I'm MIA) and adding an acceptance step when >>> someone else is required to actually run them could slow things down >>> even more. >> >> Hisham, we discussed automated smoke test platform for LuaRocks a >> couple of times previously on this list. >> >> I think that it will help here. > > Yes, it's always brought up as a nice idea, like a web-based system > for submission of rocks that would allow some system of peer reviewing > and avoid having me (and Fabio) as the bottleneck for new rocks. > Getting those implemented, however, is another story...
I'm actively working on something that does this - at least when I'm not getting sidetracked with Yak-shaving projects like the Postgres driver the app uses, and Luadoc tweaks. I should have something worth showing in a few weeks but don't want to say too much more until it's out of the vaporware phase. -Norman > -- Hisham > > _______________________________________________ > Luarocks-developers mailing list > [email protected] > http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers > , _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
