2024-01-09 Nixpkgs Architecture Team Meeting #47

[Infinisil]

• Past meeting notes
• Matrix announcement
• Lead by: @infinisil
• Meeting notes by: @infinisil
• Attendees: @infinisil @KAction @DavHau

Agenda

RFC 140

Next steps in the mass migration to pkgs/by-name:

• Merge check-by-name: Refactor to prepare for enforcing `pkgs/by-name`, make `--base` required by infinisil · Pull Request #278805 · NixOS/nixpkgs · GitHub
  • @infinisil: Started working on addressing some feedback, will push then merge once CI passes since the feedback is non-blocking
• Next significant step is [RFC 140 2a] `pkgs/by-name`: Enforce for new packages by infinisil · Pull Request #275539 · NixOS/nixpkgs · GitHub
  • Meeting to do the final review and ideal merge will be scheduled soon
  • If you want to join, add your availability here: check-by-name: Refactor to prepare for enforcing `pkgs/by-name`, make `--base` required by infinisil · Pull Request #278805 · NixOS/nixpkgs · GitHub

Naming convention for optional feature flags · Issue #148730 · NixOS/nixpkgs · GitHub

• @KAction: Wondering about standardising package flags
• @infinisil: See also Enforce that package argument defaults are applied, cleans up optional dependency convention by infinisil · Pull Request #131271 · NixOS/nixpkgs · GitHub
• Also, config can also be used for very widely needed flags
• (we had some detailed discussions)
• My recommendation: Write an RFC-like document to describe the desired approach in detail, its alternatives, advantages/disadvantages, etc.
• @KAction: Will do