Psionic K

I meant the version of cargo2nix. > It's only when fetched from git that cargo2nix errors out. Alright then, yeah, I don't know about that corner case. There's some fetch...

Lean on lazy evaluation and on-demand building. Nix won't try to evaluate everything your expressions hypothetically define, only what you put in outputs. When you ask it to build an...

Upcoming solution will make these overrideable. The present style of duplicating expressions will go away.

It can be fixed. Open up the cargo source and check the metadata code. It's output contains all of the necessary information. Consider the feature logic busted. It's going to...

Plans are in #301 and possibly other linked issues. Cargo already outputs the correct information in its metadata command. Cargo2nix uses the cargo library and basically can access all the...

Check issues tagged with high priority. I'm certain everything you're talking about is somewhere in there.

If you search around for features issues, the feature behavior is not very complete when platform dependencies exist. Check your Cargo.nix for the offending feature being passed in. Newer versions...

Holding off on this for now. There's a lot of request to configure the linker and there's already some special cases that make reading a bit taxing. I think the...

Check the CI to find the test attribute. Since the test binary is a requirement, you will find it upstream of that attribute.

Unstable has a little bit of support, baking the hash of the lockfile into the Cargo.nix. Related: https://github.com/cargo2nix/cargo2nix/issues/250 I want to be sure and kill all aspects of the problem,...