Currently, if neither %bcond_without check nor %bcond_with are set, the macro defaults to excluding dev-dependencies. This is unexpected behaviour, since it can break other macros that have the inverted default.
%bcond_without check
%bcond_with
This is mostly a problem for non-crate packages.
This was solved differently - there will be a -t flag to explicitly include test dependencies (dev-dependencies) for the %cargo_generate_buildrequires macro. This does not change the current behaviour but allows overriding the default without needing to set a bcond.
-t
dev-dependencies
%cargo_generate_buildrequires
Metadata Update from @decathorpe: - Issue status updated to: Closed (was: Open)