Closed pgajdos closed 10 months ago
CC @kstreitova @mcepl
The reason for this behavior is # SECTION
and # /SECTION
code block that is treated on the same level as conditions.
The defined order of preamble elements is
<snip>
'excludearch',
'misc',
'build_conditions',
'conditions',
'tail',
</snip>
So it means that we have misc
(where %{?sle15_python_module_pythons}
goes right now) before conditions
(where `# SECTION goes).
Btw. the only tail
macro is currently %{?python_subpackages}
so that's why this macro is at the end of the preamble.
@mcepl What is the desired place for %{?sle15_python_module_pythons}
? What about other python macros?
@mcepl What is the desired place for %{?sle15_python_module_pythons}? What about other python macros?
We usually have it somewhere close to the top.
This macro is meant to be in preamble, spec-cleaner moves it somewhere below.