GNOME Bugzilla – Bug 780324
Cargo is required by libgepub
Last modified: 2017-03-21 12:35:57 UTC
libepub depends on cargo/rust since: https://git.gnome.org/browse/libgepub/commit/?id=2461ac86dc90f29fb787655747a1f8908983567d AFAIK, jhbuild doesn't list them in its modulesets. Error output: checking for cargo... no configure: error: cargo is required. Please install the Rust toolchain from https://www.rust-lang.org/
We have decided not to depend on cargo for now, so libgepub will have to be branched.
Hey Daniel, is it possible to find a way to make Rust happen using traditional pkg-config for dependency management? cargo is not an acceptable dependency for GNOME. You don't have any branches currently that I can fall back to so I'm just going to create one, if you don't mind....
The following fix has been pushed: 0cf376a Build libgepub from git.gnome.org and from pre-rust branch
Created attachment 348364 [details] [review] Build libgepub from git.gnome.org and from pre-rust branch
Michael; when it was decided cargo is not an acceptable dependency for GNOME? Can you share a link for my own reference?
See the discussion following https://mail.gnome.org/archives/desktop-devel-list/2017-January/msg00002.html In particular: https://mail.gnome.org/archives/desktop-devel-list/2017-January/msg00011.html I think we discussed this in #release-team recently and agreed to ask the folks attending the Rust hackfest to try to find a path forward.
Maybe I should qualify that: "cargo is not an acceptable dependency for GNOME *at this time*." Further discussion is required on how to make this work for our distributors. We don't want to get into a situation where our Rust software does not get shipped.
I've updated the pre-rust branch to the 0.4 tag. It was in a commit before, the code doesn't change, only the NEWS file, but it the last commit before the introduction of Rust and there is a tag, so I think it's better to be there.
OK, thanks. We should also revert https://git.gnome.org/browse/releng/commit/?id=afb8d3af4b82b87ce8abeb99beba18dbbb4b3088 once we've figured this out.