On 10/27/25 10:25, Konrad Kleine wrote:
Hi Vitaly,
> Do you have any examples?
Yes, we use the "modern" approach for versioning in the llvm.spec [1]:
Version:
%{maj_ver}.%{min_ver}.%{patch_ver}%{?rc_ver:~%{rc_ver}}%{?llvm_snapshot_version_suffix:~%{llvm_snapshot_version_suffix}}
Since the original question was about forge macros and rpmautospec, one
example that I have that uses those macros is:
```
%global forgeurl0 https://github.com/tcbrindle/span
%global version0 0
%global date 20250521
%global commit 836dc6a0efd9849cb194e88e4aa2387436bb079b
%forgemeta
Name: span
Version: %forgeversion -p
Release: %autorelease
```
The order of `%forgemeta` relative to `%autorelease` is important, so
try to play around with it.
An example in the changelog:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2775478
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
