-
-
Notifications
You must be signed in to change notification settings - Fork 252
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
allow rec in packaging functions #762
Conversation
Deploy Preview
|
The correct resolution here would be recommending the |
What situations exist where the |
As far as I know, the |
I'd prefer to recommend |
finalAttrs also has it pitfalls like FODs used in src where it changing rev breaks the FOD which is unnoticed because the original is probably in the cache. |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-10-30-documentation-team-meeting-notes-90/34936/1 |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-11-02-documentation-team-meeting-notes-91/34938/1 |
@NixOS/documentation-team decided to avoid the confusion by not mentioning the Superceded by #790 Still, it needs better docs in Nixpkgs: NixOS/nixpkgs#266485 |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-11-09-documentation-team-meeting-notes-93/35244/1 |
The best practice on
rec
is often interpreted in nixpkgs PRs as "rewritingrec
usinglet ... in
fixes the overriding logic", whereas it isn't the case. The second pitfall is therefore less justified.In the discussion about the same topic on Discourse, the most liked post also points out that avoiding
rec
in packaging functions doesn't make much sense.Hence this PR.