2022-12-19 Nixpkgs Architecture Team Meeting #22

Nixpkgs Architecture Team Meeting #22

Notes

Sharding and other updates by infinisil · Pull Request #20 · nixpkgs-architecture/simple-package-paths · GitHub

  • @roberth: More declarative, describe the end goal
    • avoid discussing implementation details of tooling, and focus on API/structure.
    • “The unit directory contains a set of self-contained pieces of Nix code that don’t reference any files outside their own subtree”:

Sharding and other updates by infinisil · Pull Request #20 · nixpkgs-architecture/simple-package-paths · GitHub

Sharding and other updates by infinisil · Pull Request #20 · nixpkgs-architecture/simple-package-paths · GitHub

How to formally have the draft approved by every member?

  • @roberth: Everybody goes over it, makes PR’s to improve it, accept in the meeting
  • @growpotkin: make a “pre-release” branch and review as a merge?
  • @infinisil: Have 0 open issues and PRs

Read file type by aakropotkin · Pull Request #7447 · NixOS/nix · GitHub

  • @tomberek: Is this needed? If yes we might need to wait until we can rely on a Nix version with that change
  • @growpotkin: It’s only an optimization, not concerned

A way to directly traverse into the shard

@tomberek: Like pkgs.sharded.open.openoffice

  • @growpotkin: Aliasing problems, syncing one attribute with another, particularly with overrides, e.g. should pkgs.sharded.* or pkgs.* be overridden, does it apply to the other?
  • @infinisil: Can be done later, if at all needed
  • @infinisil: pkgs.hello.unitDirectory, a bit like pkgs.hello.meta.position
  • @roberth: (Relative paths?)

Action items