4 ms·
I have a strange feeling when thinking about the solution especially on macOS. The nix installation needs its store located at /nix which got harder to initiali
by larusso 4y ago
I have a strange feeling when thinking about the solution especially on macOS. The nix installation needs its store located at /nix which got harder to initialize since macOS Catalina or Mojave added the root protection. In general this is no problem when installing nix on its own. But when a wrapper tool does this and breaks the setup etc that feels hrmm problematic.
I see potential setup issues coming up with weird store error messages no normal human being being able to understand.
I really like nix and nixos. But I had already a nix setup which refused to build a rust project because of some weird linkage errors with libc or something. And I couldn’t make heads or tails out of it.
But I will check out this tool to get a better feeling. A general solution to this issue would be awesome. I would prefer JNI build support as well ;)
- grhmc 4y agoWhat do you mean about when a wrapper tool "does this"? Riff doesn't install its own Nix.
- larusso 4y agoI only checked the post so far and my understanding was that it uses nix. It is ironic that a tool who sets out to solve the issue of installing external dependencies, needs a preinstalled nix setup. My understanding was that it uses nix under the hood and the user has no real interaction with this part. But come to think of it it kinda makes sense.