It was thus said that the Great Sean Conner once stated:
>
> I just did the following in "/tmp":
>
> GenericUnixPrompt> luarocks unpack luasocket
> Warning: falling back to curl - install luasec to get native HTTPS
> support
>
> Done. You may now enter directory
> luasocket-3.0rc1-2/luasocket-3.0-rc1
> and type 'luarocks make' to build.
>
> yet the directory doesn't exist. I have no idea where LuaRocks might have
> stashed the rock. From the documentation on the website, it says it should
> be in the current directory. Yet it's not.
Okay. So here's what I found. Used to be, if I issued
luarocks unpack luamodule
If there wasn't anything in the current directory with that name, LurRocks
would search, download then unpack the module in the current directory.
That's the behavior I am expecting. It wouldn't matter if the module was
installed or not, that's how it would work.
Now though, it appears that if $HOME/.cache/luarocks DOES NOT EXIST, I get
that behavior. But, as it is created during the process, further attempts
to unpack ANY module will unpack the module in
$HOME/.cache/luarocks/<repository>/ and NOT move it to the current
directory.
-spc
_______________________________________________
Luarocks-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
