You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A partial solution I would propose to the limitation of the store path assumption is to parse the options provided to Nix to see if the user provided --store, and falling back to /. Then, append /nix/store to the end to get the store path. This wouldn't work if the store path was modified in nix.conf.
The text was updated successfully, but these errors were encountered:
I am not certain yet, but I am kinda hoping that we can get away with never looking into the nix-store ourselves and instead just query nix for data. That way environment and config will be dealt with correctly. Only thing we need to figure out is which flags need to be forwarded to internal nix calls.
Until we solve that, are NIX_REMOTE and --store the only two options which we need to consider?
You can also set store in nix.conf, which in turn is picked up from multiple locations 🫣 I absolutely agree that only going through nix would be ideal, though I suspect we'd still have to work out what the store is?
eval-store might also be relevant -- I think the drvs end up in both eval-store and store but would usually make more sense to read from eval-store...
A partial solution I would propose to the limitation of the store path assumption is to parse the options provided to Nix to see if the user provided
--store
, and falling back to/
. Then, append/nix/store
to the end to get the store path. This wouldn't work if the store path was modified innix.conf
.The text was updated successfully, but these errors were encountered: