it's underdocumented; but hugely useful
For example, I'd be super interested in some1 showing how to use the luarocks-admin command to its full potential
but it's not well maintained... some of the info in there is quite outdated
still has got some neat stuff
but at least for me it works okay as long as im doing exactly what is in there
if I want to make something different i struggle a bit
but it might be because i need to know what im doing with other tools, that arent really luarocks related, and therefore dont have to be documented there
welp, but some things i surely could
i noteiced, for example, that the docs for luarocks-admin add still document an --index flag
but that isnt at the respective terminal command help
hi, i have this problem when i execute luarocks i get Access is denied. and that it cant find 5.1 interpreter :/. i have compiled lua 5.1.5 with mingw i believe and i have it under d:\lua\5.1, luarocks lives in a neighboring directory. it doesnt show this error while i am in elevated prompt, so i suppose this is some kind of permissions issue?
luarocks 3.1.3-win32
@dracconi running with
--verbose might help us figure out what's going on wrong. There might be a bug with dealing with different drive letters, since LuaRocks is mostly tested on Unix (where there are no drive letters) and the Windows CI runs on Appveyor where everything runs off a single drive
@dracconi please run the failing command with
--verbose and paste the full output into gist.github.com then send us a link
the full output of running
luarocks config may also help
(actually, you may want to open an issue for that in github.com/luarocks/luarocks/issues and just paste there! )
I know I can
luarocks make to create a binary rock locally, but I'm curious about the same for source rocks
@paddycarey unfortunately not , currently. I'm sure it's doable, but it's slightly tricky to implement as a general feature: how to ensure you're packing just the right stuff and not your entire current working directory -- object and temp files and all -- and do it in a way that is build-type agnostic (i.e. can't assume
builtin and get the list of files from build.modules) and SCM-agnostic (can't assume git and use it to get the list of files).
I wouldn't mind accepting a patch for that feature which assumes builtin and/or git and fails gracefully with a nice error message it case it isn't using one of them.
Hey all... I'm having problems trying to manage different lua versions on my system. I used luaver to switch until now, but I started to use network namespaces now for testing purposes (ip netns NS_X exec lua -lluarocks.loader ...) but this fails as the luaver script is only available in my user shell and not as the root user.
So I was wondering how this typically done.
I tried to check the wiki, but their is little to no documentation on how to work with luarocks with different lua versions.
So I was wondering how this typically done.
I tried to check the wiki, but their is little to no documentation on how to work with luarocks with different lua versions.
Hi @wmoors, there are many ways that people go about this and indeed it can get pretty confusing! the
luarocks tool has gotten better at maintaining multiple lua versions at the same time recently, but when launching lua to run it, everything always boils down to your environment variables
the variables that matter are
LUA_PATH_5_3 and LUA_CPATH_5_3 for Lua 5.3 (with unversioned variants LUA_PATH and LUA_CPATH as fallbacks), same thing for Lua 5.2, and only the unversioned ones for Lua 5.1
the command
luarocks path --lua-version=5.x outputs the correct values for the Lua version 5.x you want to use
I don't know about the specifics of your setup to say what the values of these environment variables should be, but comparing their current values with the output of
luarocks path should lead you in the right direction!
I have been doing multiple Lua versions by using self contained LuaRocks versions. I documented it here (for windows): https://milindsweb.amved.com/LuaRocks_.html#L5 . I just need to open a command line terminal and run the batch file to initilize the environment variables. I also have a video for it: https://www.youtube.com/watch?v=403rjwb8gfc
A question I had for external dependencies packages and libraries in LuaRocks. Is there a way that we can specify compilation of an external package? Another thing is if we don't want to go the compile route can we specify the library files directly that should be downloaded for the platform? I am thinking about say LuaCURL which needs the curl library which may be compiled and also for IUP which has all the binaries of the libraries we can just download them as part of rock installation.
@hishamhm it would be nice if there is a way to run scripts or download external dependencies and specify them in the rockspec. Even though it depends from OS to OS have a method to write it in rockspec and just give some API to figure out the OS etc can open doors for developers to take care of platform dependence and make installation of complex modules more painless. LuaRocks can just enable just some mechanisms that can guve the choice to package managers to tackle this problem.
@aryajur I was thinking that a minimal first step would be to add an
error_message field for external_dependencies entries, where the rockspec author could give customized instructions. A slight complicator of putting something like a script field there would be the fact that system package managers usually need root privileges, while rocks can be installed locally.
@hishamhm I would still think that having the script option would be very useful since it allows the package creator to create and add the script. Even if the installer does not have root privilege existence of a premade script greatly simplifies installation because that script can then be passed to the system administrator who can use it and save time. Although lot of users may already have root privileges. The users I have talked to always state as this being the major hurdle for usage and getting the right packages. If the mechanism is started the problem can then slowly resolve over time for popular packages.