You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This spec file contains a section with BuildRequires: inside a conditional:
BuildRequires: update-desktop-files
if 0%{?with_new_pycups}
# All printer driver packages should have "BuildRequires: cups-rpm-helper"
# for automatic generation of Provides: tags.
BuildRequires: cups-rpm-helper
%endif
When I run spec-cleaner on it (or format_spec_file, FTM), it moves that section down below all Requires: and Obsoletes:
I wonder if that's intended behavior?
The text was updated successfully, but these errors were encountered:
This is an intended behaviour indeed, the conditions are all moved in one location in the spec. It allows for easier review of all available conditionals later on.
Basically detecting the conditions and the alphabetic sorting caused all sort of trouble with nested conditions so we had to do something that could be reliably reproducable, and this was least worst of all the posible solutions.
This spec file contains a section with BuildRequires: inside a conditional:
When I run spec-cleaner on it (or format_spec_file, FTM), it moves that section down below all Requires: and Obsoletes:
I wonder if that's intended behavior?
The text was updated successfully, but these errors were encountered: