Example of local path crate dependency?

[sthornington]

Does anyone have a working example of a cargo crate dependency in a crate_universe which is referred to by path on disk? Or any way to depend upon a local copy of a crate that you are actively working on?

I am having terrible trouble actively iterating on crates that I depend upon alongside a Bazel workspace that uses them...

[timbess]

@sthornington I had to symlink external directories into the workspace to get it to work for me.

[sthornington]

But they are still crates and lacking BUILD files? I haven't even been able to get this working... cargo-bazel gives some sort of splicing error. What version of rules_rust are you on?

[sthornington]

I can't even figure out how to get [patch] nor [replace] sections to work, crate_universe doesn't seem to accept a root [workspace] manifest as valid, since Each manifest should have a root package ...

[sthornington]

I narrowed my problem down to this code:

https://github.com/bazelbuild/rules_rust/blob/main/crate_universe/src/splicing/splicer.rs#L617-L621

... it works if I just cut that out and evaluate to false. I'm happy to submit a PR for that change, but it would be helpful to know why that logic is there in the first place ...?

@illicitonion any ideas?

[sthornington]

Never mind, that was insufficient, getting Error: The package 'Name("munge-bindings") Version { major: 0, minor: 9, patch: 4 }' has no source info so no annotation can be made now. Investigating ...

[sthornington]

I have no idea how this is supposed to work, what would it put into cargo-bazel-lock.json ? The SourceAnnotation only has arms for Http and Git. I did manage to (I think) get [patch] to work but it gives me the same error about "has no source info".

[sthornington]

@illicitonion sorry to ping you on this - hypothetically, is getting this to work something I could sponsor you or someone to do? I do a lot of co-iteration on crates and bazel projects which depend on them, so it would be very convenient to be able to change a Cargo.toml crate dependency to refer to a local relative or absolute path to the work-in-progress and have the cargo-bazel/crates_universe stuff work as expected. It could have a big red error message saying the build is currently not hermetic or whatever, but editing a crate, compiling, bumping the version, uploading to a repository, just to test the changes in the bazel build that depends on it, is a chore. Feel free to email me to follow up if you prefer.