-
-
Notifications
You must be signed in to change notification settings - Fork 17k
rhai-lsp: init at 0-unstable-2022-10-25 #434339
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
Conversation
|
Awesome! I think we should PR the |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved automatically following the successful run of nixpkgs-review
.
The upstream hasn't updated for 3 years now, I'm not sure if this is worth it. |
Okay, then please replace the lockfile here with the patch from rhaiscript/lsp#108 |
What's different from adding a |
I think patch is preferred, because it does not check in thousand of lines into nixpkgs. |
patches = [
(fetchpatch {
name = "add-cargo-lock.patch";
url = "https://github.com/rhaiscript/lsp/commit/77bd9052297d74320d84c7fcaa3fe75ddc211543.patch";
sha256 = "";
})
]; I just tried to use |
Meeeeh I forgot about that. Maybe we should just wait for rhaiscript/lsp#108 |
Upstream refuses to include a lockfile, so I would say we rather not include the package than committing thousand of lines to nixpkgs. What do you think? |
Seems like that's the only choice.
I didn't see this one coming, tho, lol. Don't know what to say tbh... I guess people are just not into build systems and don't understand how they work? |
Yep. I suggest we close this then, upstream is not interested in anyone using their software, it seems. 😢 |
I agree. Closing. |
Resolves #433006
cc @matthiasbeyer for testing
Things done
passthru.tests
.nixpkgs-review
on this PR. See nixpkgs-review usage../result/bin/
.Add a 👍 reaction to pull requests you find important.