I sorted this out for the moment that changed the dependency to the form expected by cargo publish: https://crates.io/crates/tpm2_cli
So, main goal for 0.1.2 is to fix this glitch ;-)
0
0
0
Andrew Lilley Brinker
alilleybrinker@hachyderm.io@jarkko You can do both at the same time and Cargo will handle it correctly! https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#multiple-locations
1
0
0
Ed Page
epage@hachyderm.io@jarkko On top of what was said, try using a release tool like `cargo release`. It will take care of updating the `version` field, update the lockfile, tag, etc. It is dry-run by default and with extra verbosity, you can see exactly what it will do so there are no surprises (even showing diffs of files that will be changed)
1
0
0
@jarkko you can just have both in the cargo.toml entry and local builds will use the path while published builds will use the published dependency.
0
0
1
R Tyler Croy 🦀
rtyler@hacky.town@jarkko I cannot see other replies that may have answered this already but cargo should support both of those being present at the same time for the dependency
0
0
0