| 8 Mar 2026 |
 antifuchs | waiiit why is this even getting eval'd on a darwin system | 16:02:47 |
 emily | https://github.com/nix-community/nixos-vscode-server is this the repo you mean? | 16:03:18 |
| emily | I believe this is actually caused by the combination of flake-utils + the way they're doing
pkgs = nixpkgs.legacyPackages.${system};
inherit (pkgs.lib) hasSuffix optionalAttrs;
| 16:04:30 |
| emily | rather than using nixpkgs.lib | 16:04:35 |
| antifuchs | that's the one. also, removing it as a flake input seems to have fixed my eval warnings. its outputs weren't pulled into any of my darwin systems, but ... guess these things are tied together in mysterious ways | 16:04:52 |
| emily | I think we could potentially do a Gross Disgusting Hack where we make nixpkgs.legacyPackages.x86_64-darwin.lib avoid the warning | 16:04:59 |
| emily | ah, so it's all just from that one flake? | 16:05:13 |
| antifuchs | seems so! | 16:05:27 |
| antifuchs | (it's also been unused by me since 2023, so a great reminder to remove it, lol) | 16:05:42 |
| emily | fair enough 😅 | 16:06:08 |
| emily | it could be patched to fix the warnings but I notice that it hasn't been touched in years | 16:06:19 |
| emily | so, maybe it's obsolete(?) | 16:06:23 |
 K900 | FWIW if you don't want to go the nix-ld route, all you should need is https://github.com/K900/vscode-remote-workaround/blob/main/vscode.nix | 16:07:16 |
| emily | there's a few things that can cause spurious or duplicate warnings unfortunately, I did my best to mitigate them but it's not fully avoidable. hope has just been to assess how often they happen and how annoying they are to see if this approach will work. so far few complaints, surprisingly | 16:07:20 |
| K900 | (probably updated to an appropriate nodejs version) | 16:07:33 |
|  SomeoneSerge (matrix works sometimes) changed their display name from SomeoneSerge (back on matrix) to SomeoneSerge (matrix works sometimes). | 23:34:17 |
| 9 Mar 2026 |
|  risson left the room. | 00:42:37 |
|  Norinco joined the room. | 16:23:36 |
| Norinco | I am a new nix-darwin user, and I'm currently trying to install nix-darwin and lix on my Mac. I've chosen ryan4yin/nix-darwin-kickstarter as my starter configuration. However, I noticed the following comment in the repo:
nix.enable = true; # TODO: set this to false if you're using Determinate Nix.
I don't quite understand what Determinate Nix is. My question is: if I install lix using the "New Installs" method from the official lix documentation (curl -sSf -L https://install.lix.systems/lix | sh -s -- install), do I need to set nix.enable = false?
Also, if I do set nix.enable = false, how should I configure options like substituters and gc? | 16:36:28 |
| K900 | Determinate Nix is another fork (they say "distribution") of Nix | 16:37:59 |
| K900 | You can use nix.enable = true with Lix, though you'll want to also set nix.package = pkgs.lixPackageSets.latest.lix or similar | 16:38:21 |
| Norinco | Okay, thank you for your answer. | 16:40:53 |
 nasso | i will soon get a new macbook for work, and i was thinking maybe i might bite the bullet and try out nix-darwin on it??
im pretty new to nix still, and my main concern here is multi-user support. because i want to use this machine for both work and personal stuff, i need to setup two users (unclear yet which one(s) will be admin). is this a supported use-case for nix-darwin? how will that work???
(also i have never had multiple users on macOS so i guess im also new to that part lol) | 17:24:56 |
 samasaur | we do support multiple users, yes. it should Just Work, though some nix-darwin options really only apply to the activating user so you may want to avoid those and control them with home-manager instead | 17:33:22 |
 ragdoc | You might also want to have a look at the nix.settings.trusted-users option. | 17:35:11 |
| nasso | cool! thanks! i wonder if i will regret learning nix + nix-darwin + multi-user macOS all at once | 17:37:44 |
| ragdoc | There is not much to learn on the macOS side of things, don't worry. Users can either be admins or not, that's pretty much it. | 17:40:48 |
| 10 Mar 2026 |
| Norinco | Still regarding this issue, I just took a look at the lix installer repo and noticed it says 'Based on the Determinate Installer.'(https://git.lix.systems/lix-project/lix-installer#:~:text=A%20fast%2C%20friendly%2C%20and%20reliable%20tool%20to%20help%20you%20use%20Lix%2C%20the%20community%20implementation%20of%20the%20nix%20tooling.%20Based%20on%20the%20Determinate%20Installer.) Does this mean I really should be setting nix.enable = false? | 02:45:34 |
 Randy Eckenrode | No. Det Nix has a daemon that takes over some system manage stuff. Lix relies on the user (e.g., via nix-darwin) to update it. nix.enable should be true with Lix. | 02:53:59 |
| Randy Eckenrode | The installer is just what does the initial setup (creating the store, etc). The old installer is written in Bash. The Det Nix one (also used by Lix) is written in Rust. | 02:54:53 |
