(cross-posted from the mailing list)
I’ve just put together a blog post describing some pretty awkward parts (I think) of maintaining and updating nix derivations. I’m particularly focused on cases when the nix maintainer also works on the package itself, and might need to test updates to the source code as well as updates to the derivation, since that’s what I typically do
the tl;dr is describing the motivation and basic operation of two utilities I’ve written:
- nix-pin: https://github.com/timbertson/nix-pin/
- nix-update-source: https://github.com/timbertson/nix-update-source/
But the post itself describes a pretty long journey I’ve been on to make this process simpler, and issues I’ve run into along the way. If you’ve ever found the process awkward, perhaps you’ll relate and pick up some new ideas. And if you’ve been doing this a long time perhaps you’ll think of different ways to address the problems I’ve run into - maybe there’s something I’ve missed, or a way that nix itself could be modified to make things easier, or a related issue that could be fixed at the same time.
Feedback is of course welcome either here or on the blog.