On 24.08.26 18:58, Greg Burd wrote:
The reason to carry it in-tree: Nix users are a growing segment of the PostgreSQL developer base across Linux, macOS, and increasingly the BSDs and even illumos. Today each of them keeps a private flake to hack on Postgres, I have one, and I know I'm not alone.
I don't know. Over time, people made similar arguments about Homebrew, Docker, and there will be more after this. People who are interested in this can band together and maintain it among themselves.
These private copies drift, disagree on which features to enable, and have to be re-derived every time someone new wants to contribute from a Nix machine. A single blessed flake in the tree gives everyone the same reproducible starting point and one place to keep it current, the same argument that motivates the .editorconfig and CI files we already ship.
I don't think these are good comparisons. A Nix configuration is probably of interest to on the order of 1% of developers, whereas these other things are relevant to most developers, and also importantly, changes can be verified easily by anyone, without having to learn about some new platform or tool.
