-
-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make nixos module hydra from this repository by default #1419
Conversation
When people reach out to the git repository they probably want to use hydra from the same source. This also removes the need for an overlay with simpler and more performant direct use of the nixpkgs passed in. Before it was re-importing nixpkgs. test
cc @Mindavi for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like a good improvement and I don't see any obvious mistakes. I'm personally not using the flake though.
Note I was trying to make fewer things depend on the flake before / not potentially mix Nixpkgs downstream by default. But this is fine. I realized one of the things I put in nixos-tests is not a NixOS test; that is moved out maybe that file doesn't need |
People that used the nixos module instead of the flake now have to explicitly have to set the hydra package. I believe this is less error-prone interface than assuming they imported the overlay correctly. |
hydra = nixpkgs.legacyPackages.${system}.callPackage ./package.nix { | ||
inherit (nixpkgs.lib) fileset; | ||
rawSrc = self; | ||
nix = nix.packages.${system}.nix; | ||
nix-perl-bindings = nix.hydraJobs.perlBindings.${system}; | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The duplicating of the overlay
also tripped me up, forgot to add nix-eval-jobs
in both places.
When people reach out to the git repository they probably want to use hydra from the same source.
This also removes the need for an overlay with simpler and more performant direct use of the nixpkgs passed in. Before it was re-importing nixpkgs.