On 25 February 2015 at 21:12, Geoff Leyland wrote:
>> On 26/02/2015, at 9:42 am, Hisham wrote:
>>
>> Thank you for the bug report! I filed it in the tracker.
>
> Whoops! Sorry, I should have done that myself.
No, it was my fault for giving outdated instructions; just committed this:
https://gi
> On 26/02/2015, at 9:42 am, Hisham wrote:
>
> Thank you for the bug report! I filed it in the tracker.
Whoops! Sorry, I should have done that myself.
--
Dive into the World of Parallel Programming The Go Parallel Webs
On 24 February 2015 at 08:12, Peter Billam wrote:
> Greetings again. Hisham wrote:
>> but this is a completely different thing: you're referring to
>> the repository search, I was referring about the documentation
>> material on LuaRocks itself.
>
> True; I saw the word "documentation" just when
On 25 February 2015 at 15:05, Geoff Leyland wrote:
> It checks everything else so carefully,
:-)
> but build = { type = “builtin” } causes a crash.
Indeed. Each build method should have its own type checker and launch
it by itself. Thank you for the bug report! I filed it in the tracker.
-- Hi
It checks everything else so carefully, but build = { type = “builtin” } causes
a crash.
Error: LuaRocks scm bug (please report at
luarocks-developers@lists.sourceforge.net).
/usr/local/share/lua/luarocks/build/builtin.lua:200: bad argument #1 to 'pairs'
(table expected, got nil)
stack tracebac
Greetings again. Hisham wrote:
> but this is a completely different thing: you're referring to
> the repository search, I was referring about the documentation
> material on LuaRocks itself.
True; I saw the word "documentation" just when I happened to
have been through the socket experience myse
