Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move libdnf build over to Cargo
This is now further migration towards Cargo/Rust possible
because we switched our main binary. We've had an internal
libdnf-sys
crate for a while, but now it can take overthe build of the underlying library too (like many
-sys
crates support).
This itself is just an incremental step towards migrating
the main rpm-ostree build system to e.g. cmake too (or
perhaps directly with the
cc
crate, not sure yet) anddriving it via
cargo
too.build-sys: Move -lcap linkage purely to Rust
Now that we are generating solely a Rust binary, we can
have the canonical list of things to link on the Rust side.
build-sys: Move -lstdc++ -lrt into Cargo
More draining.
build-sys: Move -lm -ldl linkage into Cargo
More Rust, less shell/m4 - the world gets slightly better.
build-sys: Drop Fedora 25+ rpm version check
I think we can just assume this nowadays.