| 16 Sep 2025 |
 toonn | matthewcroughan: I meant as an extension of the file URI scheme, file:///some/path . | 14:34:48 |
 getchoo | In reply to @joerg:thalheim.io
by making it more specific that’s what i was thinking
we could also iterate over the glob matches and use the first one that actually has a /bin/nix subpath as well to be a bit safer (since i really doubt the day will come where we have multiple nix binaries in the store during install) | 16:51:32 |
| getchoo | * this worked before the component split in 2.29 since there would only be one main nix store path at this point, but now it matches the nix-main store path first, which doesn't have a bin dir or any of the nix binaries | 16:52:24 |
 Mic92 | In reply to @getchoo:matrix.org
that’s what i was thinking
we could also iterate over the glob matches and use the first one that actually has a /bin/nix subpath as well to be a bit safer (since i really doubt the day will come where we have multiple nix binaries in the store during install) Is this not just scanning the installation tarball rather the entire nix store? | 20:22:46 |
| Mic92 | I haven't looked to deep into the code. | 20:23:13 |
| getchoo | it is, but the installation tarball now has multiple paths that match nix-* due to the component split | 20:32:59 |
| getchoo | so depending on the hashes you get, sometimes one of the components will be matched first and the installer will just blindly append the /bin/nix-store subpath to it and try executing | 20:35:12 |
