<disasm>
Why'd we switch back to single user default for nixos install on a mac?
philr has quit [Ping timeout: 244 seconds]
hamishmack has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dhess has quit [Ping timeout: 252 seconds]
Lisanna has joined #nix-darwin
hamishmack has joined #nix-darwin
dhess has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 268 seconds]
nD5Xjz has joined #nix-darwin
philr has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 244 seconds]
philr has quit [Quit: WeeChat 2.2]
nD5Xjz has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 250 seconds]
nD5Xjz has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 244 seconds]
nD5Xjz has joined #nix-darwin
<gchristensen>
is there an obviously better bashrc / zshrc file which the multi-user nix installer should write to, which macos won't erase on upgrade?
<LnL>
no, and LaunchDaemons also get cleared
<gchristensen>
jesus
<gchristensen>
:(
<LnL>
well management of the daemon has more problems, like reloading config changes
<LnL>
that's why I think there should be something that handles these 2 problems
<LnL>
there are a few small things like creating build users that only needs to happen once on a machine
<gchristensen>
right
<gchristensen>
maybe a gui service like docker ships
<LnL>
so that can happen during an installer step, but everything else is relevant for upgrading
<LnL>
I don't know what the ideas are for nix-env 2.0 but I think it should be less imperative and powerful enough to handle this scenario
<gchristensen>
oooh
<LnL>
I talked about this a bunch of times before, did I never explain it properly?
<gchristensen>
I'm not sure I understood
<LnL>
well, guess I didn't :p
<LnL>
I don't have something more concrete then than in my mind, but that seems like a better idea than rewriting the installer