public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Neal Gompa <ngompa@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/fedora-release] f45: Add optional buildrelease macro to the DistTag macro
Date: Mon, 10 Aug 2026 09:36:57 GMT [thread overview]
Message-ID: <178635461746.1.9903712047864221709.rpms-fedora-release-a058942b62d9@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/fedora-release
Branch : f45
Commit : a058942b62d9e87ff7ff5ef0b10a4b3d45371536
Author : Neal Gompa <ngompa@fedoraproject.org>
Date : 2025-12-01T18:27:43+00:00
Stats : +1/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/fedora-release/c/a058942b62d9e87ff7ff5ef0b10a4b3d45371536?branch=f45
Log:
Add optional buildrelease macro to the DistTag macro
This enables future work for automatic reverse dependency
mass builds by providing a pathway to set a value to make
each successive build of a given package input have an
increasing release value set by the build system.
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
---
diff --git a/fedora-release.spec b/fedora-release.spec
index c285dd4..cb7f0ba 100644
--- a/fedora-release.spec
+++ b/fedora-release.spec
@@ -2035,7 +2035,7 @@ cat >> %{buildroot}%{_rpmconfigdir}/macros.d/macros.dist << EOF
%%fc%{dist_version} 1
%%distcore .fc%%{fedora}
%endif
-%%dist %%{!?distprefix0:%%{?distprefix}}%%{expand:%%{lua:for i=0,9999 do print("%%{?distprefix" .. i .."}") end}}%%{distcore}%%{?with_bootstrap:%%{__bootstrap}}
+%%dist %%{!?distprefix0:%%{?distprefix}}%%{expand:%%{lua:for i=0,9999 do print("%%{?distprefix" .. i .."}") end}}%%{distcore}%%{?with_bootstrap:%%{__bootstrap}}%%{?buildrelease:+build%%{buildrelease}}
%%dist_vendor %{dist_vendor}
%%dist_name %{dist_name}
%%dist_purl_namespace %{dist_purl_namespace}
reply other threads:[~2026-08-10 9:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178635461746.1.9903712047864221709.rpms-fedora-release-a058942b62d9@fedoraproject.org \
--to=ngompa@fedoraproject.org \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox