From 80153a133d0888b7c0a7b72a9f80ccc6f005c555 Mon Sep 17 00:00:00 2001 From: Jasper Ras Date: Sat, 23 Nov 2024 17:34:50 +0100 Subject: sorted out inbox --- 0 inbox/Nix Flakes.md | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 0 inbox/Nix Flakes.md (limited to '0 inbox/Nix Flakes.md') diff --git a/0 inbox/Nix Flakes.md b/0 inbox/Nix Flakes.md deleted file mode 100644 index cb7f69b..0000000 --- a/0 inbox/Nix Flakes.md +++ /dev/null @@ -1,21 +0,0 @@ -#nix - -Nix flakes are source trees containing a file `flake.nix` at their root. The file `flake.nix` provides a standardized way to provide [[Zettelkast/Index/Nix]] artifacts. It's like a package manager for [[Zettelkast/Index/Nix]]. A flake can be dependent on other Flakes and it's possible to pin dependencies to exact revisions by using a `flake.lock` file. - -Nix flake evaluation is hermetic, meaning that it produces the same result wherever it's built.k - -The feature can be enabled in `~/.config/nix/nix.conf`: - -``` -experimental-features = nix-command flakes -``` - -To initialize in a repo: `nix flake init`. - -In flakes dependencies have to be specified explicitly and MUST be locked to specific versions therefore it's no longer allowed to use the nixpkgs found in `NIX_PATH` by referencing it like ``. - -Output of a Flake is an arbitrary [[Zettelkast/Index/Nix]] value such as a package, [[NixOS]] module or library function. -Commands `nix build` and `nix shell` will build the output `packages..default` unless we specify another output, for example: `nix shell .#checks.aarch64-linux.build`. - ---- -[Flakes Wiki](https://nixos.wiki/wiki/Flakes) \ No newline at end of file -- cgit v1.2.3