This repository has been archived by the owner on Jan 30, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Don't auto-callPackage
#6
Comments
well, we can still add a second fresh directory with different semantics when a decision is made to move away from |
From what I understand, moving files en masse leads to many merge conflicts in PRs. |
By using |
roberth
added a commit
that referenced
this issue
Oct 14, 2022
roberth
added a commit
that referenced
this issue
Nov 14, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The current proposal is rather restrictive when it comes to what's in the files.
We already established that
callPackage
has a number of issues, among which the need for default arguments to live outside the package function, and the package being defined through a function rather than a fixed point in the first place.By doing a figurative
mapAttrs callPackage
we knowingly paint ourselves into a corner.The text was updated successfully, but these errors were encountered: