| 27 Jan 2026 |
Sofie 🏳️⚧️ (she/her) | * | 08:14:37 |
vczf | In reply to @sofiedotcafe:matrix.org i want to switch off but I haven't found an integration guide to npins I’m using eval-config.nix in my /etc/nixos/default.nix. Essentially,
let
system = “x86_64-linux”;
pins = import ./npins;
pkgs = import pins.nixpkgs { inherit system; };
in
import “${pins.nixpkgs}/nixos/lib/eval-config.nix” {
inherit pkgs;
modules = [ ./configuration.nix ];
}
Then nixos-rebuild -f /etc/nixos switch works fine. My actual config is more complex with per-host modules and overlays and import-tree and a fun mess, but that’s the bones | 08:58:51 |
vczf | Here’s my flake alias lol:
fk = “nix --extra-experimental-features flakes”;
| 09:00:59 |
vczf | I’ve been avoiding flakes the second time around since it wasn’t helping me understand nix code in general | 09:01:59 |
vczf | * I’ve been avoiding flakes the second time trying to learn nix since it wasn’t helping me understand nix code in general | 09:02:17 |
neobrain | Why aren't you enabling it in your nix.conf directly? | 09:29:52 |
neobrain | (Or in configuration.nix) | 09:30:26 |
vczf | I don’t need it except occasionally. I use comma instead of nix run and , -s nix shell | 09:47:12 |
vczf | * I don’t need it except occasionally. I use comma instead of nix run and , -s rather than nix shell | 09:47:25 |
vczf | My biggest lifesaver with this config so far is DankMaterialShell being upstreamed into nixpkgs. Not sure if I’d have been able to figure out how to integrate their flake into my config | 09:50:22 |
neobrain | that's the nix-command feature, not flakes. Enabling either feature doesn't disable the "old" interfaces afaik. but whatever works for you :) | 09:52:22 |
vczf | You need flakes enabled in order to nix run nixpkgs#cowsay hello
Unless I am mistaken, that nixpkgs is a reference to the system flake registry entry for nixpkgs | 10:01:38 |
neobrain | right | 10:29:26 |
| Jez (he/him) 🐦⬛ joined the room. | 10:51:59 |
| 13 May 2024 |
| zrsk joined the room. | 13:37:30 |
| dariof4 joined the room. | 14:16:05 |
| abbe joined the room. | 14:42:22 |
mjm | lix is now in nixos-unstable, what's the best way to use it in a NixOS config? | 15:47:41 |
K900 | nix.package = pkgs.lix | 15:47:54 |
K900 | Probably | 15:47:58 |
K900 | Or just keep using the module | 15:48:02 |
puck | you can use nix.package = pkgs.lix; if you want; but using the overlay will guarantee more updates (tho less binary cache) | 15:48:44 |
mjm | well, the module/overlay doesn't easily support using the one from nixpkgs | 15:48:44 |
mjm | i do want more binary cache | 15:49:21 |
mjm | yeah i guess i'll just do nix.package then | 15:50:43 |
raitobezarius | to have binary cache and HEAD, we will probably need to track the channels and bolt a lix on there and rebuild with our own CI then push in our binary cache | 17:33:17 |
Charles | What's lix using as its binary cache? Attic? | 17:34:36 |
| Arian left the room. | 17:37:44 |
@tc424:glasgow.social | Last I heard they were using garage as the back end, and think about attic | 17:39:11 |
@tc424:glasgow.social | I don't know if that means they're just pushing directly into garage's s3 interface for the moment | 17:39:36 |