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
I thik that it would be good to add mapping ~ part of the version to %{PREVERSION} macro if version string contains ~.
It will allow standarise using that mechanisms across all spec files to have syntax like
With that it will be possible to only update Version: line.
Probably it would be good to ad the same logick between %{preversion} and %{PREVERSION} as it is now between %{version} and %{VERSION}.
The text was updated successfully, but these errors were encountered:
Closing.
After few experiments I founfd that using ~ in version for non-release builds makes spec files more complicated so curretly it does not simplifies anything.
I thik that it would be good to add mapping ~ part of the version to %{PREVERSION} macro if version string contains ~.
It will allow standarise using that mechanisms across all spec files to have syntax like
With that it will be possible to only update
Version:
line.Probably it would be good to ad the same logick between
%{preversion}
and%{PREVERSION}
as it is now between%{version}
and%{VERSION}
.The text was updated successfully, but these errors were encountered: