-
Notifications
You must be signed in to change notification settings - Fork 108
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
Adding the overlay of a nix flake #28
Comments
The semantics for pulling overlays from other flakes should be improved, but for now anything added to nixflk's overlays output attribute is automatically added to the NixOS system overlays. So simply wire the overlays from the repo you mentioned into said overlays attribute and they'll be available for you. |
Sorry for my late comment to this, but it is still not totally clear to me how to do so. I saw the example of a custom overlay at https://github.com/nrdxp/nixflk/blob/993a79e61edeb811537927cbb504769013eaf37d/profiles/laptop/default.nix#L48-L61, but:
In the end I've added the overlay in the overrides section there, but I would like to hear other people's opinion on that. |
Right here. Something like:
I'm thinking about adding an internal "extras" flake that is not exposed to the outside world but is wired into the default config so adding things from other flakes can be less painful. Until then, this should do. |
I'm reopening to close with a PR I am about to submit. Essentially, I have added an |
Fixes #28 by adding an `externOverlays` list to easily import overlays from external flakes.
Fixes #28 by adding an `externOverlays` list to easily import overlays from external flakes.
Fixes divnix#28 by adding an `externOverlays` list to easily import overlays from external flakes.
👋 This template gave me the right boost to start porting my client machine configuration to flakes, many thanks!
I would like to add the overlay that another nix flake provides, e.g., nixpkgs-wayland.
What would be the most optimal way to do so? Since I am talking about packages that both system and user (via home-manager configuration) might use, I am particularly interested in a solution which addresses both cases.
The text was updated successfully, but these errors were encountered: