-
-
Notifications
You must be signed in to change notification settings - Fork 438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] /run symlink necessary? #941
Comments
I'm not sure but I could have sworn there used to be a module option to disable (opt-out) the creation of |
Unless it's not mentioned in Darwin Configuration Options it seems that one was removed. |
I don’t think we have a specific configuration switch for this. I believe the only obstacle to us using It would also be nice if we could hide the synthetic |
I was afraid that 'hard coded /run path' was a reason - sad though given that pretty much most common build systems used by the majority of packages support specifying or auto-detecting the appropriate path for their runtime state (--runstatedir for autoconf for example). Looking into hiding /run so far was fruitless on my end - synthetic.conf only allows you to create links in the root volume but since it's read-only outside of that process I couldn't find a way to change attributes of the generated link later on. I still appreciate that this issue isn't just brushed off as 'can't be helped' :) |
In this case the “upstream” is Nixpkgs passing paths like I’d prefer to just use the native paths as long as we can maintain compatibility with upstream packages, or if it turns out that the things it breaks shouldn’t really be relevant on macOS, although there’s an argument that we might break random scripts that expect the NixOS paths and I do want to prioritize having the same interfaces as NixOS when practical. |
I don't pretend I have nearly enough knowledge about the inner workings of nix-darwin but I was wondering if the /run symlink it adds to /etc/synthetic.conf is really necessary or if it wouldn't actually be more in the spirit of targetting darwin / macOS to directly refer to /private/var/run?
I'm mainly asking because the way /run is created also makes it so it can't be hidden from Finder either (
sudo chflags -h hidden /run
does not work because the symlink is part of the read-only root volume).The text was updated successfully, but these errors were encountered: