The Nixpkgs Architecture Team (NAT) is there to solve architectural nixpkgs issues that are too big in scope for any single person to undertake. There are regular 30 minute meetings every Wednesday (currently 13:30 to 14:00 UTC) in Jitsi Meet, open for anybody to join, recorded and live-streamed to YouTube, meeting notes are committed to a repository and added as a reply here.
The agenda for the NAT is generally created from discussions in the past week, mostly on Matrix, but you’re also free and encouraged to suggest additional topics by replying to this thread.
Tentative Agenda
Some items are propagated from last weeks meeting as there was not enough time for all of them.
In-person meeting at Nixcon
An ad-hoc in-person NAT meeting was held last week at Nixcon. Present were @Infinisil, @roberth, @tomberek, @Ericson2314, @j-k, @fricklerhandwerk, @DavHau, though I think there was somebody else too. @tomberek took some notes which he can hopefully share soon. Main takeaways were:
- @fricklerhandwerk proposed to really focus on just one thing and ignoring everything else.
- @fricklerhandwerk also proposed for @Infinisil to officially take the lead of the team.
- We also discussed various tradeoffs and possibilities with the auto-called-packages RFC implementation
The Nixpkgs Architecture Team is on nixos.org now
In a PR to the nixos.org homepage, a section about the NAT was added to the website: Nixpkgs Architecture Team | Nix & NixOS. Now duplicated on the website, the information is removed from the original team page in another PR.
Problems with RFC 127
RFC 127 is in the FCP now, though @Infinisil is not happy with it as it seems to make deprecations throw errors immediately without warning for a release.
JSON schema for NixOS options
@Profpatsch proposed to have a JSON schema for NixOS options, which would allow them to be written with auto-completion in a JSON file. @DavHau, @nbp, @whentze and @piegames were also involved in the discussion. At Nixcon @Profpatsch hacked on this.
Type-checked wrapped fetchers experiment
@Growpotkin updated his wrapped fetchers draft code, e.g. fetchGit. More details and a usage example can be seen in the readme
Handling argument escaping with setup hooks
Originally discussed with @winter in PR #189539, it’s unclear what the convention should be for passing arguments properly to setup hooks. This was also brought to attention on Matrix. @danielbarter was also interested. @Growpotkin and @winter discussed new NPM tooling following that.
Active RFC drafts
In addition to the agenda, this post can bring attention to the existing RFC drafts of the NAT. Feel free to open issues/PRs in these repositories if you want to bring something to attention relating to that RFC draft. Alternatively feel free to chat on Matrix or reply here on Discourse.
-
Auto-called packages: Make most attribute definitions in
pkgs/top-level/all-packages.nixbe auto-generated from a single flat (or prefixed) directory instead, where the subdirectory corresponds to the attribute name. The ad-hoc category-based structure of packages will be removed.