| 17 Apr 2024 |
|  JoelMcCracken joined the room. | 16:29:02 |
|  K900 changed their display name from K900 ⚡️ to K9Ö0. | 17:16:42 |
| K900 changed their display name from K9Ö0 to K900. | 17:21:53 |
| K900 | 17:21:54 |
| 24 Apr 2024 |
|  cole-h joined the room. | 14:17:38 |
| 25 Apr 2024 |
|  David Mell (zraexy) joined the room. | 23:22:59 |
| David Mell (zraexy) changed their display name from David Mell to David Mell (zraexy). | 23:52:06 |
| 26 Apr 2024 |
|  pxc changed their display name from pxc to pxc (why). | 23:32:11 |
| pxc changed their display name from pxc (why) to pxc. | 23:32:18 |
| 27 Apr 2024 |
| pxc set a profile picture. | 00:46:06 |
| pxc removed their profile picture. | 00:48:06 |
|  @ygt:matrix.org joined the room. | 18:23:12 |
| 29 Apr 2024 |
|  NixOS Moderation Botchanged room power levels. | 15:29:21 |
| 1 May 2024 |
| NixOS Moderation Botchanged room power levels. | 15:06:27 |
| 2 May 2024 |
|  @nick_kadutskyi:matrix.org joined the room. | 17:16:44 |
| @nick_kadutskyi:matrix.org set a profile picture. | 21:19:10 |
| 6 May 2024 |
| @nick_kadutskyi:matrix.org changed their display name from nick_kadutskyi to nickkadutskyi. | 17:33:25 |
| @nick_kadutskyi:matrix.org left the room. | 17:35:38 |
| 8 May 2024 |
 abathur | Matthew Kenigsberg & cole-h: given the events that were unfolding week before last I have not tried to pester the infra team or made other noteworthy progress on open issues--so I'm thinking we can skip this session unless either of you have something specific? | 02:02:24 |
| cole-h | I'm fine with either | 02:03:02 |
 Matthew Kenigsberg | I did https://github.com/NixOS/experimental-nix-installer/pull/15 today - looks like we may need to tweak the actions so I could use input on those | 02:05:43 |
| Matthew Kenigsberg | I also wasn't 100% sure on the tarball stuff | 02:06:24 |
| abathur | ok, sounds like we'll have stuff to look at | 04:00:19 |
| pxc | how nutty would it be to have a Nix installer attempt to get nix-daemon.sh's environment changes handled by an init system/session manager, if available, rather than plugging directly into a shell?
Fish users who are Nix novices (and maybe also Unix novices) have struggled getting their shell to 'nixify' properly forever. I've tried to work on it, and helped get something usable going for NixOS which is now also used in Nix-Darwin. But people still struggle, many years later, and other fun new shells (Elvish, Nushell, PowerShell, Xonsh, idk) face similar problems with Nix's POSIX initialization scripts
I think we could easily have the Nix stuff happen before the user session starts with systemd on Linux and launchd on macOS
| 06:37:25 |
| pxc | * how nutty would it be to have a Nix installer attempt to get nix-daemon.sh's environment changes handled by an init system/session manager, if available, rather than plugging directly into a shell?
Fish users who are Nix novices (and maybe also Unix novices) have struggled getting their shell to 'nixify' properly forever. I've tried to work on it, and helped get something usable going for NixOS which is now also used in Nix-Darwin. But people still struggle, many years later, on foreign Linux and macOS. Other fun new shells (Elvish, Nushell, PowerShell, Xonsh, idk) face similar problems with Nix's POSIX initialization scripts
I think we could easily have the Nix stuff happen before the user session starts with systemd on Linux and launchd on macOS
| 06:38:13 |
| pxc | The experimental new installer is already willing to get creative with this kind of stuff to avoid breakage on macOS, and I think it was a good choice. | 06:39:06 |
| abathur | Have you tried setting this up with launchctl (and on what macOS version?)
It sounds like (thanks to cole-h for finding my own past comments about this :)) we are hemmed in on the global environment point by macOS these days, see for example:
- https://github.com/canonical/multipass/issues/2417#issuecomment-1553437799
- https://github.com/cachix/install-nix-action/issues/183#issuecomment-1595055643
| 14:38:41 |
| abathur | but if you've got it working on a newer macOS, perhaps they caused trouble for someone important and had to back off from the change? | 14:39:37 |
| pxc | In reply to @abathur:matrix.org
but if you've got it working on a newer macOS, perhaps they caused trouble for someone important and had to back off from the change? I do, but I don't think that's quite it, since I actually do get that error on my system (macOS 14.4.1)
This works:
- setting per-user session variables interactively with
launchctl setenv via LaunchAgents as my user (works immediately; close and relaunch your terminal emulator and it'll pick up the variables)
- settting per-user session variables interactively with
launchctl setenv in LaunchAgents that run as root
- setting global session variables with
launchctl setenv in LaunchAgents that run as root (takes effect with next session)
but this doesn't work:
- interactively using
launchctl setenv as root, which yields the message Could not set environment: 150: Operation not permitted while System Integrity Protection is engaged
| 15:46:35 |
| pxc | I was assuming the restriction of launchctl setenv was limited this way from the start, but now that I think of it, maybe it was totally removed, then only partially backed off | 15:48:15 |
