-
Notifications
You must be signed in to change notification settings - Fork 8
Add Cargo.lock #108
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
base: master
Are you sure you want to change the base?
Add Cargo.lock #108
Conversation
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Wouldn't the lock file be regenerated upon build if it is not included? |
The lock file, as the name suggests, is for locking dependencies. If it is not included, a build is not reproducible for example. For more rationale, look here: https://doc.rust-lang.org/cargo/faq.html#why-have-cargolock-in-version-control |
I understand the concept of keeping the lock file in version control, but I am not convinced that it is absolutely necessary. And any "last-good" version will likely be outdated very quickly, and novice users building it themselves may not remember to do a |
In this case, this package will not be included in any distros. |
I don't know enough about this to comment... I understand you mean that the distro author would want a reproducible build? Anyhow, this crate is work-in-progress, and is not release-ready. Those who uses it are likely to be cloning it locally and building themselves. We can worry about packaging it when it is done... |
Yes
I'll suggest to close the nixpkgs PR then. |
Not sure what that is... Can you elaborate? I admit I didn't write this repo and not familiar with it. |
just stumbled on this while trying to integrate (and use) rhai in one of my rust projects. To elaborate: there is (was) an open PR by @yzhou216 to package rhai-lsp for nixos (NixOS/nixpkgs#434339) and Matthias reached out to let you know that the Cargo.lock file is missing. Without the lock file it is not possible to reliably reproduce what the author(s) of this crate used or intended to have when building the crate. So it actually is common practice to just commit it. While I must admit that this project is not in a good shape, it would nevertheless be good if we could get this going again, as there seems to be still interest in rhai and also this lsp.
🎸 |
Yes, I agree that we should get someone to pick up the LSP repo. Users have been asking for it and I don't know enough myself to keep it going. Would appreciate any interest in restarting this development. As for packaging for a distro, I am quite sure this repo is so outdated and feature lacking that it won't be a good idea... |
This is needed for packaging and it is also normal to add the lockfile, so lets do it.