cargo-ebuild
cargo-ebuild copied to clipboard
gentoo
[MIRROR] cargo extension that can generate ebuilds using the in-tree eclasses
Closes: #35 @thesamesam looks fine to me, I decided to call this 0.6.0 and do some other housekeeping. There doesn't seem to be any unit tests but the output against...
cargo.eclass now supports `@` as a delimiter between package name and version as it's faster to parse and is already common in Rust world. Also, `${CARGO_CRATE_URIS}` should be used in...
This is just a paper cut, but I imagine the fix is easy enough.
cargo.eclass will now support GIT_CRATES see https://github.com/gentoo/gentoo/pull/29289 cargo_ebuild could pre-fill such information. or at least provide data for templating engine to fill it via template.
Sometimes a project uses a git dependency. cargo-ebuild should handle simple cases of git deps.
`$ cargo ebuild` on https://github.com/Michael-F-Bryan/mdbook-linkcheck generates among other things this snippet: ```ebuild # ... DESCRIPTION="A backend for `mdbook` which will check your links for you." # ... ``` Note the...
Running `cargo-ebuild ebuild --noaudit` in the cloned https://github.com/rust-lang/rust-bindgen.git repo with tag v0.63.0 checked-out causes `cargo-ebuild` to hang indefinitely without producing any output. If I run it through `ltrace`, I see:...
cargo-ebuild chokes on workspace projects ( https://github.com/alacritty/alacritty is an example ), make sure it can generate a ebuild for a project that uses workspace.
/usr/bin/cargo-ebuild defaults to fetching data for audit, to warn about vulnerable crates. While this is a good thing I believe, it can cause tricky to debug segfaults as reported in...
https://github.com/cardoe/cargo-ebuild/issues/30 https://bugs.gentoo.org/709568 Some binding -sys crates are known to build private copy of a library by default, or if it's not found. cargo-ebuild could maintain a list of know offenders...