Skip to content

Expose flake interface that does not rely on overlays #124

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

Merged
merged 5 commits into from
Sep 13, 2023
Merged

Conversation

Mic92
Copy link
Member

@Mic92 Mic92 commented Sep 13, 2023

As creator of small tools, my flakes might often end up in other peoples
projects. Overlays are a performance problem in those use cases because
it would kept re-instantiating nixpkgs instances. Of course I could also
expose my stuff as overlays as well.

In that case I would need to merge downstream dependencies like
go2modnix as well, which would pollute their nixpkgs instance with
unrelated stuff and also make it harder for my users to tell what random
attributes came from which place.

As creator of small tools, my flakes might often end up in other peoples
projects. Overlays are a performance problem in those use cases because
I would kept re-instantiating nixpkgs instances. Of course I could also
expose my stuff as overlays as well.

In that case I would need to merge downstream dependencies like
go2modnix as well, which would polute their nixpkgs instance with
unrelated stuff and also make it harder for my users to tell what random
attributes came from which place.
@Mic92 Mic92 merged commit f95720e into master Sep 13, 2023
@Mic92 Mic92 deleted the revise-interface branch September 13, 2023 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant