Search Criteria
Package Details: cargo-all-features 1.10.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/cargo-all-features.git (read-only, click to copy) |
---|---|
Package Base: | cargo-all-features |
Description: | A Cargo subcommand to build and test all feature flag combinations |
Upstream URL: | https://crates.io/crates/cargo-all-features |
Licenses: | MIT, Apache-2.0 |
Submitter: | LuckyTurtleDev |
Maintainer: | LuckyTurtleDev (msrd0.dev) |
Last Packager: | msrd0.dev |
Votes: | 1 |
Popularity: | 0.000003 |
First Submitted: | 2023-03-05 19:13 (UTC) |
Last Updated: | 2024-04-07 14:17 (UTC) |
Dependencies (3)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
Latest Comments
yochananmarqos commented on 2023-03-06 14:58 (UTC)
@msrd0: I didn't catch what the difference was at first. Sorry for the noise.
LuckyTurtleDev commented on 2023-03-06 13:25 (UTC)
@yochananmarqos
cargo check --all-features
does check with all features flags enabled.cargo check-all-features
does check each possible combination of feature flags.msrd0 commented on 2023-03-06 10:56 (UTC)
@yochananmarqos Please take the time to read the description of this crate carefully. It includes the difference between it and running builtin commands with
--all-features
: https://crates.io/crates/cargo-all-features#whyyochananmarqos commented on 2023-03-05 21:06 (UTC)
What is the point of this crate to begin with let alone why it's useful as an AUR package? How is it any different than the built-in
--all-features
flag?