Section cargo.crates should be fully replaced on update with the output of cargo2port <path/to/Cargo.lock> command (cargo2port is regularly updated in MacPorts)
Expected Cargo.lock location inside tree must be provided by developer. In some cases could be guessed, but I'll leave guesses to be an extension rather than a base implementation.
This file might be absent, then it should be generated using cargo generate-lockfile [options], where options are almost always the same provided for installation and usually are -p <project>, listed in build.args-append.
Full command might be provided to replace cargo generate-lockfile generation.
Section
cargo.cratesshould be fully replaced on update with the output ofcargo2port <path/to/Cargo.lock>command (cargo2portis regularly updated in MacPorts)Expected
Cargo.locklocation inside tree must be provided by developer. In some cases could be guessed, but I'll leave guesses to be an extension rather than a base implementation.This file might be absent, then it should be generated using
cargo generate-lockfile [options], where options are almost always the same provided for installation and usually are-p <project>, listed inbuild.args-append.Full command might be provided to replace
cargo generate-lockfilegeneration.