<cbarrett> if I install something like freetype or harfbuzz with nix-darwin, does that only install the binary components in /run/current-system/...? Or are the libraries symlinked somewhere too, so I can link to them while building non-nix things?
<LnL> libraries are not linked anywhere to avoid weird stuff like that
veske has joined #nix-darwin
hamishmack has joined #nix-darwin
veske has quit [Ping timeout: 248 seconds]
hamishmack has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hamishmack has joined #nix-darwin
__Sander__ has joined #nix-darwin
nefix has joined #nix-darwin
__Sander__ has quit [Ping timeout: 272 seconds]
__Sander__ has joined #nix-darwin
domenkozar[m] has joined #nix-darwin
<domenkozar[m]> LnL: dropped off due to regnick irc, let me know if you had some feedback
<LnL> I didn't do much with the heat of the past week
<LnL> but I think there are 2 edge cases I didn't think about before
<LnL> 1. anything that gets replaced, like bashrc, would cause problems if the user wants to uninstall nix entirely
<LnL> 2. changing the original nix.conf breaks a multi-user install if the nix-daemon service isn't explicitly enabled
<LnL> the latter can be verified with a sanity check, but the former is a bit more tricky unless the installer adds a source line to some more files
<domenkozar[m]> doesn't nix-darwin have uninstaller?
<LnL> yeah
<domenkozar[m]> it could go per each backup and ask to restore
<LnL> or restoring the files there, that's also an option
<domenkozar[m]> or just restore the file as a copy instead of symlink
<domenkozar[m]> yeah
<LnL> don't remember if you kept that part, basically the assumption is that if a file references it's /etc/static counterpart it doesn't need to be replaced, avoiding the uninstall issue
<domenkozar[m]> didn't touch that apart :/
<domenkozar[m]> part*
<domenkozar[m]> LnL: so uninstalled should choke on that?
<domenkozar[m]> uninstaller*
<LnL> no it doesn't touch the file either, so the source line will still be there
<LnL> but that's not a big deal and it's not a link so removing nix wouldn't break the symlink
<domenkozar[m]> so /etc/static -> /nix/store/72xpd4j0cykrpyibk22i11iq65mhb6kj-etc/etc
<domenkozar[m]> that one needs to be replaced then
<domenkozar[m]> I guess that's already done
<LnL> maybe I shouldn't worry this much about it and have the installer just restore the backups
__Sander__ has quit [Ping timeout: 245 seconds]
nefix has quit [Remote host closed the connection]
johnw_ has joined #nix-darwin
johnw has quit [Ping timeout: 252 seconds]
<LnL> hrm, that broke the tests somehow :(
daGrevis has quit [Quit: daGrevis]
* cbarrett LnL: ty, i thought thatd be the case
<cbarrett> oops, misfire on the option return aka /me
rizary_ has joined #nix-darwin
<LnL> you can link it if you really want, but keeping a shell or result symlink in your project is much better IMHO
<cbarrett> Yeah, a result symlink + then passing an option to configure seems relatively robust at least for now
<cbarrett> May resort to homebrew if that is still sketchy.
<cbarrett> thanks for the pointers :)
<LnL> exactly with that your stuff won't break if you update the system and it can potentially be used by other people
<LnL> a channel update + gc would remove the libraries you linked against
<LnL> building from nix-shell has similar problems, I always keep a root around for the drv to avoid that
<cbarrett> +1