← Back to context Comment by bialyalibaba 2 days ago Nixpkgs should reduce package count. Waiting 2 days for unbound CVE patch merge is unbearable. 6 comments bialyalibaba Reply pasc1878 2 days ago They could improve that speed if they had more hardware to do the needed rebuilds.I hope you are paying them something. bouk 2 days ago You don't have to wait? You just have to compile matter yourself Diti 2 days ago Ask your favorite LLM to write an overlay for whichever package you need patches applied for before they hit Nixpkgs. amarshall 2 days ago Use nixos-unstable-small branch or backport the change and build yourself. shim__ 2 days ago There needs to be another repository with less stringent standards, nixpkgs should be for core libs and system applications Cyph0n 2 days ago That’s where flakes come in.Flakehub is one attempt at solving the discovery problem. For example: https://flakehub.com/flake/nix-community/disko?view=usage.
pasc1878 2 days ago They could improve that speed if they had more hardware to do the needed rebuilds.I hope you are paying them something.
Diti 2 days ago Ask your favorite LLM to write an overlay for whichever package you need patches applied for before they hit Nixpkgs.
shim__ 2 days ago There needs to be another repository with less stringent standards, nixpkgs should be for core libs and system applications Cyph0n 2 days ago That’s where flakes come in.Flakehub is one attempt at solving the discovery problem. For example: https://flakehub.com/flake/nix-community/disko?view=usage.
Cyph0n 2 days ago That’s where flakes come in.Flakehub is one attempt at solving the discovery problem. For example: https://flakehub.com/flake/nix-community/disko?view=usage.
They could improve that speed if they had more hardware to do the needed rebuilds.
I hope you are paying them something.
You don't have to wait? You just have to compile matter yourself
Ask your favorite LLM to write an overlay for whichever package you need patches applied for before they hit Nixpkgs.
Use nixos-unstable-small branch or backport the change and build yourself.
There needs to be another repository with less stringent standards, nixpkgs should be for core libs and system applications
That’s where flakes come in.
Flakehub is one attempt at solving the discovery problem. For example: https://flakehub.com/flake/nix-community/disko?view=usage.