Skip to content
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

Can the number of inputs/dependencies be lowered for the Flake? #445

Open
toastal opened this issue May 15, 2024 · 4 comments
Open

Can the number of inputs/dependencies be lowered for the Flake? #445

toastal opened this issue May 15, 2024 · 4 comments
Labels
question Further information is requested

Comments

@toastal
Copy link
Contributor

toastal commented May 15, 2024

I have included a different project into my flake that had this project as a input & now my flake lock has exploded with new things I need to audit. Are all of these inputs actually required?

@sandydoo sandydoo added the question Further information is requested label May 15, 2024
@sandydoo
Copy link
Member

sandydoo commented May 15, 2024

Could you please elaborate on this? What is your definition of "exploded" and which inputs do you consider redundant?

We're aware that the project ships with two versions of nixpkgs. We'd like to remove at least one of them at some point. Other than that, there's only 5 6 inputs...

@toastal
Copy link
Contributor Author

toastal commented May 15, 2024

flake-utils probably isn’t needed either

@toastal
Copy link
Contributor Author

toastal commented May 15, 2024

I believe there are zero-dep alternatives to flake-compat too

@sandydoo
Copy link
Member

Sure, we can replace flake-utils with the common forAllSystems function. I can merge that in, PRs welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants