rhai-lsp: init at 0-unstable-2022-10-25#434339
Conversation
|
|
Awesome! I think we should PR the |
|
matthiasbeyer
left a comment
There was a problem hiding this comment.
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-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.