Hisham Muhammad

The behavior difference here is intentional: `--lr-path` and `--lr-cpath` provide only the entries derived from the `rocks_trees` list, so that the user can prepend or append it to the rest...

You don't even need to run a clone of luarocks.org as Thijs suggested. A rocks server just needs to be a HTTP (or `file://`!) accessible URL containing rock or rockspec...

Also, if for some reason one wants to force `LUA_LIBDIR` to be present on systems where it is needed but not autodetected, there's `luarocks config link_lua_explicitly true`.

@teto I don't think I have said it publicly it anywhere, but my intention is to port LuaRocks to Teal. I understand it is a significant undertaking, but having control...

@teto Thanks for reporting on your experiences! > thanks for the update. Is there a working teal codebase already ? Not yet! > I am a bit anxious because it...

Not sure what we can do about this. It's a known gotcha for Lua... Filed this one under the "semantics" label because it's the one we use for "surprising behaviors",...

Right now the only way to do this is to share an API key for a luarocks.org user. Since yhat givrs permissions over all of the user's projects, one way...

@technomancy Done!!

@svermeulen @Nukiloco This PR was merged into the `next` branch, along with a bunch of other features! For backwards compatibility, I've added `--feat-arity=off` flag, which allows for the more lax...

I'm closing this PR since we'll be getting functionality to address similar use-cases via the `interface` type as already implemented in the `next` branch! Thank you all for the brainstorming...