Due to issue in #10, we need to make some patch to crate before metadata gets parsed (otherwise cargo metadata just crashes).
cargo metadata
In case of libc, we do:
libc
diff -uNr libc-0.2.20.orig/Cargo.toml libc-0.2.20/Cargo.toml --- libc-0.2.20.orig/Cargo.toml 2017-01-17 17:58:14.000000000 +0100 +++ libc-0.2.20/Cargo.toml 2017-02-12 15:49:12.461756105 +0100 @@ -16,6 +16,3 @@ [features] default = ["use_std"] use_std = [] - -[workspace] -members = ["libc-test", "libc-test/generate-files"]
I'm not sure what would be best workflow for doing this.
Does it mean we have to remove the "workspace" section every time? What about just loading the whole file and deleting the whole section?
@msehnout it was just example when cargo metadata fails. Which means we can't generate spec file.
Basically I'm searching for some option or such for initial patching. which will let cargo metadata work.
ACTION: ignatenkobrain to experiment with approaches, compare them and choose the best (ignatenkobrain, 21:54:06)
Metadata Update from @ignatenkobrain: - Issue assigned to ignatenkobrain
Metadata Update from @ignatenkobrain: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
rust2rpm -t fedora-26 -p libc will open text editor and do all magic itself.
rust2rpm -t fedora-26 -p libc
Login to comment on this ticket.