Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

What is the correct way to use luarocks? #1527

Closed
wushu037 opened this issue Aug 13, 2023 · 1 comment
Closed

What is the correct way to use luarocks? #1527

wushu037 opened this issue Aug 13, 2023 · 1 comment

Comments

@wushu037
Copy link

I'm having two problems

  1. some modules are downloaded with names that don't match the names used by require. E.g. luarocks install luasocket -> require("socket")
  2. does luarocks offer the ability to manage multiple versions of a module? I didn't find a description.

This can be difficult when doing collaborative development and long term development. So:

  1. do I need to add a file to the project that describes which modules are used in the project?
  2. Since there is no version management, it is possible that everyone in the team installs a different version of the module at a different time, so should I put the module in the project directory?

I need to hear from the luarocks team.

@alerque
Copy link
Contributor

alerque commented Aug 14, 2023

You already got a serviceable answer to this question when you asked it on the wrong repository. I don't think you "need" to hear specifically from the LuaRocks term. That is the answer: you can setup a rockspec for your project that specs exactly the versions you need that version to use, then have everybody install those via the appropriate options and optionally into a tree specific to the project.

@luarocks luarocks locked and limited conversation to collaborators Feb 17, 2024
@hishamhm hishamhm converted this issue into discussion #1574 Feb 17, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants