Re: Has wsapi updated and removed the use of "module()"?

[Fabio Mascarenhas <mascarenhas@...>]

Ryan, are you mixing git HEAD and stable versions of the WSAPI rocks? I have been updating WSAPI for Lua 5.2 (avoiding deprecated features like module) in the git HEAD, but have not touched the rockspecs in the official repository, so people not using the bleeding edge rocks on http://luarocks.org/repositories/rocks-scm should not be affected.

--
Fabio Mascarenhas

On Sat, Mar 23, 2013 at 12:42 AM, Ryan Pusztai <rpusztai@gmail.com> wrote:

Hi,

I am having problem using the LuaRocks version of Xavante and wsapi-xavante. When I try to start Xavante with:

    .../sandbox/lib/luarocks/rocks/wsapi-xavante/1.5-1/bin/wsapi 

Give me this error:

    lib/luarocks/rocks/wsapi-xavante/1.5-1/bin/wsapi:41: attempt to index field 'util' (a nil value)

stack traceback:

...box/lib/luarocks/rocks/wsapi-xavante/1.5-1/bin/wsapi:41: in main chunk

[C]: ?

I looked at the files a bit and it looks like WSAPI might have gotten updated for Lua 5.2 support and didn't update the wsapi-xavante rock. The main thing seems to be the removal of using the "module(...)" function so you can't just "require()" them anymore. I hope I am just tired, but it seems completely broken.

--

Regards,
Ryan

--
You received this message because you are subscribed to the Google Groups "Kepler Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kepler-project+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.