| 19 Feb 2026 |
samasaur | In reply to @validitymaiden:matrix.org Is it ok for nix-darwin to follow nixos-unstable or does it have to follow some variant of *-darwin? It will work but the channel blockers are different and you will probably have a better time following a non-nixos-specific channel | 19:15:37 |
samasaur | For unstable, the corresponding channel is nixpkgs-unstable | 19:16:07 |
validitymaiden | I've been using nixpkgs-unstable for nix-darwin, but I'm now trying to add my this to a monolithic flake for all my systems and I'm not sure how to handle the inputs. For example: nixos on a few platforms with home-manager and nixos-wsl which follow nixos-unstable and nix-darwin on macos, also with home-manager, following nixpkgs-unstable. | 19:43:26 |
validitymaiden | I suppose I'd have to have a bunch of different inputs and the downstream modules would need to use the one appropriate for which channel to follow. | 19:45:01 |
samasaur | yes :( | 19:48:04 |
validitymaiden | Well, no worse than the 2 overlays I have, I guess π
| 19:48:33 |
samasaur | yeah it is ugly but in practice you can ignore it most of the time | 19:49:57 |
validitymaiden | Yeah, I'll get there. Been making good progress with it and so far I'm very impressed tbh. Hopefully I can get proficient enough to start contributing soon. | 19:54:05 |
Sarah Clark | I'm reviewing https://github.com/NixOS/nixpkgs/pull/486412/ to see if it builds on Darwn. It fails in the frontend build when fetchPnpmDeps returns a different hash on Darwin vs. linux. Any ideas for resolving this? | 20:12:35 |
Sandro π§ | it should definitely use fetcherVersion 3 | 20:21:53 |
Sarah Clark | Thank you. Testing that so I can suggest the change in a review | 20:22:32 |
Sandro π§ | I think 2 fixed a general darwin issue which works for most packages but we should definitely straight jump to 3 | 20:22:55 |
Sarah Clark | Definitely. Confirmed that 3 fixes the issue, will drop a suggested change on the PR | 20:26:37 |
Sarah Clark | Thanks for your help | 20:27:50 |