From 04cce295ef63c650fef8f1b531eec136bcea2301 Mon Sep 17 00:00:00 2001 From: isabel Date: Sat, 18 Jan 2025 12:50:46 +0000 Subject: [PATCH] fix: spelling errors --- content/im-not-mad-im-disapointed.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/im-not-mad-im-disapointed.md b/content/im-not-mad-im-disapointed.md index b46efd6..7cb88cf 100644 --- a/content/im-not-mad-im-disapointed.md +++ b/content/im-not-mad-im-disapointed.md @@ -19,8 +19,8 @@ again. ### `system` and `lib.nixosSystem` Often I see people passing the `system` argument to `lib.nixosSystem`. However, -you should not do this! This is beacuse "legacy input" and will straight up be -ignored beacuse of your autogenerated `hardware-configuration.nix` file, which +you should not do this! This is because "legacy input" and will straight up be +ignored because of your autogenerated `hardware-configuration.nix` file, which will set system for you. So to rectify this we can instead set `nixpkgs.hostPlatform` to the desired system. @@ -124,10 +124,12 @@ yourself if you ever get here. Instead, overlays should be consumed like hello = pkgs.callPackage ./default.nix { }; }; + # this is bad x86_64-linux.default = final: prev: { hello = pkgs.callPackage ./default.nix { }; }; + # this is still bad default.x86_64-linux = final: prev: { hello = pkgs.callPackage ./default.nix { }; }; @@ -169,9 +171,9 @@ All the time I see people writing some form of the following: Both of these `pkgs` are bad. Importing `nixpkgs` without a system will use `builtins.currentSystem` which is impure, this means that it needs to use -information that may not be reproducable like your system type. And the second +information that may not be reproducible like your system type. And the second `pkgs` is explicit importing `nixpkgs` with `system`, which is not as -preferable but not strictly speaking "bad". Instead, consider writing: +preferable but not strictly speaking “bad”. Instead, consider writing: ```nix { -- 2.51.2