-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
feature foo needs feature bar #43
Comments
You can do this already by specifying this dependency in the feature section of [features]
foo = ["bar"]
bar = [] In the construction of the feature set matrix, this dependency is currently not taken into account (see discussion in #25), and the sets If you want this dependency not for your crate, but only for the testing matrix, then this is currently not possible, but I am working on a PR that will add more flexibility of restricting the feature matrix. |
…e selected feature sets Fixes frewsxcv#25. Fixes frewsxcv#43. BREAKING CHANGE: As previously feature sets [B], [A,B] were included separatly, now there will only be [A,B] run if A is a dependency of B. The testcase [B] is redundant, as it activates feature A automatically.
I created now the PR #50, which would allow to specify this dependency only for the purpose of testing: [package.metadata.cargo-all-features]
rules = [
"bar => foo"
] See README in that PR for more details on this feature. |
…e selected feature sets Fixes frewsxcv#25. Fixes frewsxcv#43. Even though cargo activates dependent features automatically, we can reduce the amount of feature sets when already resolving these dependencies during creation of all feature sets. We decide to go for the more verbose option, selecting [A, B] over [B] when A is a feature dependency of B. This allows an easier implementation, as dependency chains C -> B -> A can be verified one by one, and it takes other rules like skip_feature_sets correctly into account without modification. BREAKING CHANGE: As previously feature sets [B], [A,B] were included separatly, now there will only be [A,B] run if A is a dependency of B. The testcase [B] is redundant, as it activates feature A automatically.
…e selected feature sets Fixes frewsxcv#25. Fixes frewsxcv#43. Even though cargo activates dependent features automatically, we can reduce the amount of feature sets when already resolving these dependencies during creation of all feature sets. We decide to go for the more verbose option, selecting [A, B] over [B] when A is a feature dependency of B. This allows an easier implementation, as dependency chains C -> B -> A can be verified one by one, and it takes other rules like skip_feature_sets correctly into account without modification. BREAKING CHANGE: As previously feature sets [B], [A,B] were included separatly, now there will only be [A,B] run if A is a dependency of B. The testcase [B] is redundant, as it activates feature A automatically.
…e selected feature sets Fixes frewsxcv#25. Fixes frewsxcv#43. Even though cargo activates dependent features automatically, we can reduce the amount of feature sets when already resolving these dependencies during creation of all feature sets. We decide to go for the more verbose option, selecting [A, B] over [B] when A is a feature dependency of B. This allows an easier implementation, as dependency chains C -> B -> A can be verified one by one, and it takes other rules like skip_feature_sets correctly into account without modification. BREAKING CHANGE: As previously feature sets [B], [A,B] were included separatly, now there will only be [A,B] run if A is a dependency of B. The testcase [B] is redundant, as it activates feature A automatically.
I have a feature
foo
which required also featurebar
to be enabled.It looks like this can not be tested with cargo-all-feautures currently.
At the moment you can skip all combination of feature
But I can not do something like this:
Alternative a new
deps
field can be added:The text was updated successfully, but these errors were encountered: