Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent behaviour when executing luarocks in different directories #1526

Open
wushu037 opened this issue Aug 13, 2023 · 1 comment
Open
Labels

Comments

@wushu037
Copy link

wushu037 commented Aug 13, 2023

version: LuaRocks 3.9.2

I didn't find a description of the problem I'm having in the rocks usage documentation. So I don't know if luarocks is doing this on purpose or if it's due to a bug.

The situation is that executing luarocks commands in the luarocks installation directory (and any subdirectories) does not produce the same behaviour as executing luarocks commands in other directories.

For example:

  • Executing luarocks install ... in the luarocks installation directory, the module will be installed in the luarocks installation directory /lua_modules. while executing this command in other paths, the module will be installed in /usr/local. The subpaths all conform to rock's tree structure.
  • Only if you execute luarocks path in the luarocks installation directory, the resulting rules will contain entries that match the luarocks installation directory/lua_modules path.

It's as if the two directories are two different environments. If it's a bug, I hope it's fixed, and if it's intentional design, I'd like to know where the documentation related to it is?

@hishamhm hishamhm added the docs label Feb 17, 2024
@hishamhm
Copy link
Member

Yes, the design is intentional. The documentation is unfortunately lacking (and help would be much appreciated!) but here is a summary from the original design document: https://github.com/luarocks/luarocks/wiki/Project:-LuaRocks-per-project-workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants