I see a few processes around here that grab packages from another package manager and “nixifys” them. See nixpkgs/r.section.md at 2149ad5bdfa57b29135c1bf4ffa54d4eaa629730 · NixOS/nixpkgs · GitHub and I'm retiring from Haskell maintenance in Nixpkgs
Is there a way to automate these sorts of pull requests that consist of running a script to update a package set?
My process today was: notice an R package is broken and needs updating, realize that to update an R package the “easiest” thing to do is to bump all packages pulled from cran. Realizing that this process hasn’t run since January, and in the meantime there was a patch introduced as a “quick fix” for one package without updating the whole set, which broke the tool to update the whole set.
I’m worried that this sort of thing would turn away users who aren’t already 100% sold on the nix mission. I ended up “undoing” the quick fix and updating the whole package set (resulting in bump cran by Jake-Gillberg · Pull Request #121819 · NixOS/nixpkgs · GitHub), but this was really more time than I was expecting to spend on nix today, and I still don’t have the correct dependency included in my project because overriding in this scenario seems a bit complicated
It sounds like @peti had some personal automation going on already. Would it make sense to extend this strategy and automate some of these processes “officially”? What would that take? I’m willing to help, but don’t know enough about the current processes of nix release / maintenance to know where to start.