-
Notifications
You must be signed in to change notification settings - Fork 350
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
Support local overlays #478
Comments
My other option was doing all the chaining myself
in my devenv.nix |
I was thinking to add |
This feature is necessary for me to use devenv instead of manual flake.nix 😄 |
You can do this using inputs:
subflake:
url: path:./subflake
overlays:
- default and in {
outputs = { ... }: {
overlays.default = self: super: {
hello2 = self.hello;
};
};
} Then your { pkgs, ... }: {
packages = [ pkgs.hello2 ];
} |
To avoid that boilerplate we could support overlays:
- myoverlay1: |
self: super: { hello2 = self.hello; }
- ./myoverlay2.nix |
Another possibility would be to evaluate This would provide a better API (allowing us to provide overlays per module) for sacrificing performance (to be measured how much). |
Relevant is #792 because we need to import nixpkgs once. |
Would be great to support local overlays in the repository.
I have to override a package that depends on another package etc.. and doing it with an overlay is very simple.
My workaround at the moment is:
and I have to use pkgs1 everywhere.
The text was updated successfully, but these errors were encountered: