Some projects use path-based dependencies, but do not actually set up a workspace that contains those paths / sub-crates. This is currently not supported by %cargo_generate_buildrequires, because it does not recursively resolve dependencies for path-based dependencies, and instead relies on metadata from cargo metadata - but this metadata does not contain information about path-based dependencies if they are not also listed as workspace members.
%cargo_generate_buildrequires
cargo metadata
Note that implementing this would require distinguishing between path-based dependencies on crates that are workspace members and path-based dependencies on crates that are not workspace members.
Log in to comment on this ticket.