-
Notifications
You must be signed in to change notification settings - Fork 17
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
feat: lockfile support #244
base: master
Are you sure you want to change the base?
Conversation
Review ChecklistDoes this PR follow the Contribution Guidelines? Following is a partial checklist: Proper conventional commit scoping:
If applicable:
|
🤔 maybe we should just call the file |
I just can't get the test cases to succeed (╯°□°)╯︵ ┻━┻ It looks like it could be something to do with the neovim scheduler? Not sure how to get busted working with that. |
167af51
to
0132598
Compare
|
55b05d6
to
403b485
Compare
Todo:
|
Looks like luarocks is ignoring the |
6de88ea
to
b05dded
Compare
Blocked by luarocks/luarocks#1662 |
Looks like luarocks/luarocks#1662 has been fixed, so this is now unblocked |
We're going to have to wait for luarocks 3.11.1 to land in nixpkgs. |
Well... it looks like luarocks 3.11.1 is still not picking up the lockfile when installing 😞 |
Closes #34.
The documentation says luarocks will use a lockfile if there is one in the cwd.
But I haven't confirmed this yet.
This needs some vigorous testing.
How it works
Adding/updating/removing rocks:
--pin
flag to theinstall
commandSyncing rocks:
cwd
to the location of the lock file for anyinstall
commands