daylin/oizys
1
0
Fork 0
mirror of https://github.com/daylinmorgan/oizys.git synced 2024-09-29 00:07:18 -05:00
Code Issues Projects Releases Packages Wiki Activity

clarify the point of flakes

Browse source
This commit is contained in:
Cole Mickens 2020-10-25 14:47:13 -07:00
parent 47cd27000e
commit 3ed917054d
No known key found for this signature in database
GPG key ID: B475C2955744A019
1 changed files with 12 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -1,8 +1,18 @@
# nixos-flake-example # nixos-flake-example
This shows how to build the same config, with and without flakes. This shows how to build the same config, with and without flakes. And shows that both builds produce the same output.
It also shows that `flake.nix` is basically just some syntax. It also shows that `flake.nix` is basically just some syntax. In this case,
we are using flakes to bring our NixOS system config (`configuration.nix` and `hardware-configuration.nix`)
into a single repository *along with* the `nixpkgs` reference used to build the system. Without flakes,
`nixpkgs` is ... well, potentially unknowable.
The point of flakes is to:
1. remove `NIX_PATH` and all of the indirection that comes with it
2. encourages pinning by use/creation of `flake.lock` automatically with the use of `nix` commands
3. enables fully hermetic Nix projects were all dependencies are specified
4. allow pure evaluation (again, enabling hermetic projects)
5. pure evaluation allows for Nix expression caching, leading to nice UX performance gains
You can run `./check.sh` to show that this builds the same system config You can run `./check.sh` to show that this builds the same system config
with/without flakes. with/without flakes.