Hi, I'm new to the Lua universe, having been asked to help bring support for LuaRocks into our product development process. I'm a release engineer with Circonus, and we run a SaaS monitoring/trending/analysis platform which embeds Lua in a couple of key components. We also sell a private, on-premise version of the product for larger enterprises to operate for themselves. For this reason, everything we require for a SaaS install has to be delivered as an OS package.
I've been trying to understand how a rock gets installed on the system and grapple with how we might translate that into a package. What I'm wondering about is the function of the manifest file, and whether luarocks supports a concept like Perl's MakeMaker "pure install", which avoids creating a local log of what was installed. The point is that end users won't be running luarocks themselves to install rocks-- they'll do a package install instead, and the rocks dependencies will be translated into package dependencies. This avoids having to have a full build environment on every system, and eliminates the need to reach out to various internet sources, which isn't possible for most of our on-premise environments. I hope that makes sense, and if anyone here is familiar with how other OSes (if any) package rocks, I'd love to know more about it. It looks like Ubuntu delivers some Lua modules (penlight, filesystem, etc.) but they don't appear to be using luarocks to do it. Color me confused... :) Eric ------------------------------------------------------------------------------ _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
