Cannot generate the `with_problematic_crates` Cargo.nix sample about crate2nix HOT 3 CLOSED

Hmm, good question.

So, unfortunately, the cargo metadata command generates "opaque package IDs" which include local directory paths (see known issues in README). So these changes are expected.

The rest are not. Especially the libPath = "lib.rs" things should not be added since e2a0cc6, I guess?

In general, some of the changes could be explained by a cargo update but I did not see changes in the Cargo.lock file. I would hope that cargo produces reproducible output for cargo metadata with a given lockfile (except the packe ID problem).

from crate2nix.

Any ideas how to follow up on this?

from crate2nix.

Maybe you can try executing the "./regenerate_cargo_nix.sh"

from crate2nix.