rpms
/
systemd
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Use %version_override/%release_override to specify version/release by users 

When backporting the latest changes to CentOS Hyperscale reviewers
were confused by using %version and %release to define "Version" and
"Release" which are supposed to specify the values for %version and
%release. Let's use different macros to make it more clear that these
are supposed to be set by users building the rpm and add a comment
to explain why we do this.
This commit is contained in:
Daan De Meyer 2024-02-20 12:20:11 +01:00
parent 7740aea610
commit 0a51fe1e6b
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
systemd.spec
View File

@ -33,8 +33,10 @@
Name: systemd
Url: https://systemd.io
Version: %{?version}%{!?version:255.3}
Release: %{?release}%{!?release:%autorelease}
# Allow users to specify the version and release when building the rpm by
# setting the %%version_override and %%release_override macros.
Version: %{?version_override}%{!?version_override:255.3}
Release: %{?release_override:%{release_override}%{?dist}}%{!?release_override:%autorelease}
%global stable %(c="%version"; [ "$c" = "${c#*.*}" ]; echo $?)