elmPackages.elm-coverage: drop#415911
Conversation
elm-verify-examples doesn't depend on elmi-to-json anymore.
I did not commit changes to node-composition.nix, which didn't seem intended.
70a7765 to
8eb258b
Compare
|
So, to regenerate the node packages to remove elm-coverage, I had to update them first before. But since a few packages were broken, I couldn't really verify the updates... thus I fixed this brokenness first. |
|
|
Looks good now, the only question remaining is: Are we OK with dropping |
|
Seems fine to me. |
|
I think there is no way elm-coverage could be kept going forward. So if it's not really question of if we can drop it but when we can drop it. |
|
Why are you removing elm-instrument in the same PR and without further comment in the commit messages?
|
|
The only reason elm-instrument was packaged was as a dependecy of elm-coverage. It's not useful for anything else not even as a stand alone thing. |
|
Yeah, I basically removed everything that was not used anymore after removing elm-coverage. But you're right, I could have written a bit more about that in the commit message. |
This allows dropping elmi-to-json, which in turn allows dropping GHC 8.10.7. Along with elmi-to-json, we can remove the patchBinwrap utility, which was only used for that purpose. Along with elm-coverage, we can also drop elm-instrument, which was only used as a dependency of the former, and it's reverse dependency indents.
8eb258b to
9404d8d
Compare
|
Adjusted the commit message accordingly, no other changes. |
35c090c
into
NixOS:haskell-updates
|
Interesting. It was just removed without any stub "here was elm-coverage but no longer". vs |
As discussed in #413234, one option is to drop
elm-coverage.I first tried to drop only
elmi-to-json, but didn't succeed (#413234 (comment)).Part of tracking issue: #346214
Things done
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usageAdd a 👍 reaction to pull requests you find important.