6

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?

you are viewing a single comment's thread
view the rest of the comments
[-] silver@lemmy.brendan.ie 5 points 1 year ago

Maybe try submitting patches to the source project or nixpkgs?

[-] rutrum@lm.paradisus.day 1 points 1 year ago

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 points 1 year ago

Well it's just two files, and it doesn't touch anything else. I think they might welcome it more than you think

this post was submitted on 08 Sep 2023
6 points (100.0% liked)

NixOS

1016 readers
1 users here now

NixOS is a Linux distribution built on top of the Nix package manager. Its declarative configuration allows reliable system upgrades via several official channels of stability and size.

This community discusses NixOS, Nix, and everything related.

founded 2 years ago
MODERATORS