We can't yet handle crates that use [workspace] paths, because those paths are not included in *.crate packages, yet cargo metadata still looks for them.
[workspace]
*.crate
cargo metadata
This might be considered a cargo bug. Not all cargo commands work on bare crate packages, especially with path dependencies, although cargo metadata does work in that case.
rayon
[workspace
num
Future note, rayon stopped using [workspace] in its git master -- not sure why. Another example crate using this is libc, which is even more important for us to package.
libc
ACTION: jistone to followup on cargo's handling of unpacked *.crate packages (jistone, 21:11:05) AGREED: just drop [workspace] thing for now in libc crate (ignatenkobrain, 21:12:03)
Thinking about this a bit more and... How do we handle initial creation of spec for libc?
Any suggestions which options to add to rust2rpm?
Cargo has been trimming path and [workspace] when publishing since cargo#4030, release 0.20.0. So most crates these days should be published in a more friendly state already.
path
Metadata Update from @ignatenkobrain: - Issue close_status updated to: Won't Fix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.