I would like to note that this is about the online flake registry — #170 would be the issue to discuss about writing that kind of thing in flake.nix. If online flake registries were banned…
I don't think reading environment variables and local paths is really in the same category as the flake registry. Impure evaluation is very often something you genuinely want — even if you…
nix repl --file
What on earth. You don't get error: flag '--file' requires 1 argument(s), but only 0 were given? Why is Rust in there? This is wild. Do you have @jade's external nix-doc plugin loaded maybe?
Ah I understand what you're saying now yes. It would be less disruptive, but I don't really see the point. Indirect lookup to write a lockfile isn't a great idea and we'd rather just give an easy…
Oh gods we don't need more basic daily usage commands that require --impure
Yes in the codebase it is also technically a flake lock, even absent any notion of tarball-ttl its technically the same mechanism
No such file or directory in flakes is a terrible error message
Our branch does this: cdc1a66e31/src/libexpr/flake/flake.cc (L224)
No such file or directory in flakes is a terrible error message
Found our branch: [19993398a1...Qyriad:nix:cdc1a66e31c499506f6de4c7d8718ff09b105655](https://github.com/Qyriad/nix/compare/199933…
:write to nix repl
Minor complication worthy of note: the REPL supports lines of the form key = value that add bindings scoped to the REPL session, which can be overridden with later commands. These would need to…
The flake registry is still really handy for command-line usage so I can't imagine wanting to drop it entirely. But command-line usage doesn't require actually locking flakes, which is the thing…
Update: the Boost rpath references in $out/lib were apparently "normal" — at least in the sense that the libs were not built differently than they should have been.
The old build system…
No such file or directory in flakes is a terrible error message
We have a branch somewhere that adds the filepaths involved in IO errors to the relevant exception classes and uses it in the error message.
@rbt's structured errors PR would probably be a…