Closed jbedo closed 3 years ago
I'd say a branch in nixpkgs is preferable as it makes contributing, sharing the work among multiple people and changes in maintainers easier.
cc @grahamc @domenkozar who can make these kinds of changes.
I'd rather see the branch to be on nixpkgs for two reasons:
It may also be a good idea to move r-nixpkgs.nix
from peti/ci
to nixpkgs as, say, pkgs/top-level/release-r.nix
, so the jobset can be changed with less hassle.
We should expand the platforms to darwin & aarch64 too if there's capacity.
All done, I think.
I'd like to request a change to the configuration of the r-updates jobset (https://hydra.nixos.org/jobset/nixpkgs/r-updates) to alter the nixpkgs input to point at the r-updates branch in my fork (https://github.com/jbedo/nixpkgs.git) rather than peti's. As one of the current codeowners of r/rPackages I would like to be able to manage staging and testing of this tree.
Moving r-updates to a branch of nixpkgs rather than my fork, as is done with haskell-updates, would also be fine with me if that's more appropriate.