<Mic92_>
I would like keep the evaluation checks as safety measure, in case people doing mistakes.
<tilpner>
By default, sure. But maybe with exceptions?
<tilpner>
Limiting package-set.nix to only provide stuff that evals should work, eventually
<tilpner>
But I was hoping to get rust-overlay into NUR quickly, as I was hoping to use it for another thing :/
<Mic92_>
for what?
<tilpner>
I'll use the rust-overlay directly for now, and switch to NUR when ready
<tilpner>
A little qemu+nix sandbox toy
<Mic92_>
I hope nobody is trying to reference other nur repositories from there own. Cycles would be terrible to debug.
<Mic92_>
*their
<tilpner>
You mean I couldn't have an NUR package that uses nightly from the mozilla NUR repo?
<Mic92_>
I would not suggest to pull it from nur but rather import it yourself. We would need a better explicit interface to handle dependencies on other repositories.
<Mic92_>
nix is not really a constraint solver.
<tilpner>
I don't think it would have to be, for this. There is only one version of each repo, and nixpkgs does the "tying the knot" dance all the time
<infinisil>
Might be interesting to write one in Nix :P
<tilpner>
:c
<Mic92_>
infinisil: well, carnix tried that.
<Mic92_>
it can become very complex and maybe slow.
<Mic92_>
I am not sure how haskell handle this.
<infinisil>
Tried means it didn't work out and isn't used?
<Mic92_>
it does not work in all cases.
<infinisil>
Huh
<Mic92_>
and the expressions are rather large, but this is probably more specific to rust.
<tilpner>
Doesn't carnix do the dependency solving in Rust, and then output the resolved Nix expression?