Every now and then I see a program that doesn't have a default.nix or flake.nix in the source, doesn't have an entry in nixpkgs, and otherwise can't find a derivation for. So I write them myself.
What's the best way to share these? Should I contribute to nixpkgs? (does this count if I'm making flakes?) Do I maintain a single repo for each program? Or do I create a repo with a collection of flakes? Something else?
6 Comments
silver@lemmy.brendan.ie · 5 pts · 2y
Maybe try submitting patches to the source project or nixpkgs?
rutrum@lm.paradisus.day · 1 pts · 2y
I've thought about submitting to the source but I imagine that dumping two files in the root directory for a build tool that the devs don't use or even know about is a hard PR to get merged. But maybe that's not even the optimal way to distribute flakes, and it ought to be in a different place altogether, like nixpkgs or flakehub.
thedeadwalking4242@lemmy.world · 2 pts · 2y
Well it's just two files, and it doesn't touch anything else. I think they might welcome it more than you think
pol@infosec.pub · 4 pts · 2y
https://flakehub.com ?
rutrum@lm.paradisus.day · 1 pts · 2y
I'm only just now looking at publishing on flakehub. It does look like many users can point at individual repositories that just package external software. It looks like this encourages a repository for each application. Thanks for suggesting.
Cyberflunk@lemmy.world · 3 pts · 2y
rutrum@lm.paradisus.day · 1 pts · 2y
This is certainly an option, just wondering whats done most in practice. Right now this is what my own flakes do.