| 19 Aug 2023 |
 Zhaofeng Li | * For example, when you only edit networking.hostName, the new system profile closure is mostly identical to the old one except for a few paths | 19:26:11 |
| Zhaofeng Li | The same applies to just adding new packages. Or are you asking about something else? | 19:26:55 |
 @khalilsantana:matrix.org | My question is centered around package versions rather than anything else. Say all my hosts have foo-bar-v1.0, then at a later point the nixos-channel provides foo-bar-v2.0, since the config.nix didn't change I don't think colmena will fetch & apply the new binaries to the remote hosts, correct? | 19:29:07 |
| @khalilsantana:matrix.org | Or does a colmena apply also applies package upgrades, not only installs/uninstalls? | 19:29:50 |
| Zhaofeng Li | Nix works fundamentally differently from other package managers. The package versions are decided when you evaluate the expression, and for Colmena everything is evaluated locally on the host you are deploying from | 19:31:33 |
| Zhaofeng Li | so with channels, it will follow whatever you have on the machine running colmena | 19:31:59 |
| @khalilsantana:matrix.org | Pretty neat! So I guess I don't need to do anything special, just run an apply once in a while | 19:33:55 |
| @khalilsantana:matrix.org | (I've seen there's an auto-upgrade option in nixos itself, but I'd rather have more control) | 19:34:29 |
| Zhaofeng Li | As a more concrete demonstration, run nix-build '<nixpkgs>' -A hello and you will get a path. This path is unique to this specific version of hello, tied to everything that it depends on:
$ nix-store -qR /nix/store/qi2wm8z1m8c8x164ki6r4fbpfl7is735-hello-2.12.1
/nix/store/2y9zl8ky5ac28ali6ly1zfz11d4fq48b-xgcc-12.3.0-libgcc
/nix/store/ic9wnagwh22yhqh3lcdlnv5m178w6f0f-libunistring-1.1
/nix/store/a9mxddm4a5p4kp84vys4n2nrmwqgk7kr-libidn2-2.3.4
/nix/store/1x4ijm9r1a88qk7zcmbbfza324gx1aac-glibc-2.37-8
/nix/store/qi2wm8z1m8c8x164ki6r4fbpfl7is735-hello-2.12.1
| 19:37:53 |
