has anyone seen an explanation of nix flakes that explains the design goals of flakes & the fundamental problems they're trying to solve before diving into the syntax?

i'm looking for something like:

* the goal of flakes is to let people define packages in an uncoordinated way without a central repository
* the problem is that coordinating dependencies: you could easily end up with an explosion where you end up installing 1000 versions of libc
* the way flakes address that problem is ???

Follow

@b0rk

@delroth who might know

In case you're also looking for an answer to your last question alone: if a flake defines an overlay, it can naturally say "use the libc from the nixpkgs I'm being overlaid on" with all the benefits and warts of that.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.