-
Notifications
You must be signed in to change notification settings - Fork 413
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
flake: add overlay #11192
base: main
Are you sure you want to change the base?
flake: add overlay #11192
Conversation
So that consumers can more simply use the packages exported by this flake, by adding the overlay when they instantiate nixpkgs. Signed-off-by: Lorenzo Manacorda <lorenzo@mailbox.org>
Signed-off-by: Lorenzo Manacorda <lorenzo@mailbox.org>
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.
I think this sounds reasonable. I'm just unsure about adding dune
to pkgs.dune
as the overlay.
@anmonteiro would you prefer it were called |
I'm not sure. I'm happy to try it out like this until anyone complains. |
@@ -46,18 +46,11 @@ | |||
configureFlags = [ "-native-compiler" "yes" ]; | |||
}); | |||
}) | |||
self.overlays.default |
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.
not the biggest fan of applying the own overlay when declaring pkgs
. can we do it another way? maybe a common function that both the overlays and outputs
call.
So that consumers can more simply use the packages exported by this flake, by adding the overlay when they instantiate nixpkgs.
I think a cleaner way (which would avoid the ugly
//
at the end) would be to get rid of flake-utils entirely, taking inspiration from rust-overlay.But that is a bigger change.