On Wed, Sep 15, 2010 at 03:42, Hisham <[email protected]> wrote: > On Tue, Sep 14, 2010 at 9:24 AM, Alexander Gladysh <[email protected]> wrote: >> On Mon, Sep 13, 2010 at 21:59, Hisham <[email protected]> wrote: >>> On Mon, Sep 13, 2010 at 2:12 PM, Hisham <[email protected]> wrote:
>>>> I'm about ready to release LuaRocks 2.0.3, but I'd like some feedback >>>> from the LuaRocks community before releasing it to lua-l: >>> http://luarocks.org/releases/luarocks-2.0.3-rc2.tar.gz >> A problem: LR asks user to report a bug if CTRL+C is pressed during >> some operation: >> $ sudo luarocks install luaposix 5.1.2-1 >> ^C >> Error: LuaRocks 2.0.3 bug (please report at >> [email protected]). >> /usr/local/lib/luarocks/share/lua/5.1//socket.lua:102: interrupted! > I could not reproduce this -- perhaps LuaSocket catches Ctrl-C by > raising an error? Perhaps. Easy to test: create a fake rock and point it to a port open by, say, netcat. This way you should have time to press ^C while LuaSocket tries to get data from there. > That would be odd, but in this case then what can we > do? Parse the error message? > >From my attempts, depending on what external command was running when > you press Ctrl-C, LuaRocks fails with various errors: <...> > I'm leaving this behavior as is for LR 2.0.3, but does anyone have any > idea on how to improve this? Set our own signal handler? Alexander. _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
