Let's say a rust package has build features [a, b, c, d].
I want to remove a.
Is my only option

buildNoDefaultFeatures = true;
buildFeatures = [ "b" "c" "d" ];

?

This seems quite flaky to me. There is no buildDisabledFeatures ?

In reply to@glepage:matrix.org

Let's say a rust package has build features [a, b, c, d].
I want to remove a.
Is my only option

buildNoDefaultFeatures = true;
buildFeatures = [ "b" "c" "d" ];

?

This seems quite flaky to me. There is no buildDisabledFeatures ?

In reply to@glepage:matrix.org
Sure, but this doesn't prevent us from forgetting to check what upstream does and forget to add newly introduced default feature to our white-list, right ?

In reply to @morj:morj.men
No it doesn't. But in general if you have a major version upgrade, you can't be sure that your code using it will still work. This situation is no different

Well, I would argue that the code I used in the PR can either:

• succesfully remove the vendored_curl default feature
• fail (I used --replace-fail)

I don't see how it could "silently do something different)

Well, I would argue that the code I used in the PR can either:

• succesfully remove the vendored_curl default feature
• fail (I used --replace-fail)

I don't see how it could "silently do something different"

Would it make sense to have a disabledTests attribute in buildRustPackages (similar to the one of buildPythonPackage) ?

checkFlags = [
  "--skip=foo::bar::baz"
  "--skip=bonjour::au_revoir"
];

->

disabledTests = [
  "foo::bar::baz"
  "bonjour::au_revoir"
];