Description
Is your feature request related to a problem? Please describe.
The nix package defined here locally in flake.nix uses a bunch of custom dependencies that the packages upstream in Nixpkgs also have to use. Do they need to be different? Usually not, I would suppose.
By using the upstream Nixpkgs packages, upstreaming patches and configuration into Nixpkgs, we get some binary caching for free despite overriding the nixpkgs input, while also improving consistency between the package here and there, which is great for troubleshooting.
Describe the solution you'd like
Use Nixpkgs packages directly, reuse patched stuff from Nixpkgs, and/or upstream local changes into Nixpkgs.
Describe alternatives you've considered
Let the configurations diverge.
Additional context
Full disclosure: my x86_64-darwin builds are really slow
Priorities
Add 👍 to issues you find important.