[Rpm-maint] [rpm-software-management/rpm] Use git tags to determine RPM version strings (PR #4178)

[Michal Domonkos]

dmnks left a comment (rpm-software-management/rpm#4178)

Now, let's say we would just go with the cmake-only variant (with a new pre-release label). That way, nothing would really change in our workflow, other than "bumping" the pre-release label (if any) instead of bumping the awkward 5.90.99 kind of version. So that's indeed the simplest way :smile: 

However, we would have to decide how to handle the development snapshots. Let's suppose we have released the 6.1.0 alpha1, branched off shortly after, and bumped the version in cmake to 6.2.0 on master.  There's two ways to reset the pre-release label now:

1. Set it to empty
2. Set it to "dev" (or similar)

If we set it to empty, then the runtime version (and development tarballs) will say "6.2.0" which is of course wrong. Therefore, setting it to "dev" would indicate that it's a development snapshot, however we would have to remember to do this manually whenever bumping the version itself, which seems annoying... 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4178?email_source=notifications&email_token=ADLPZUZGIUWYOOVDMR7OESL4XCADLA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRZGQ3TKMRWGEZKM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOS2XA4S7MNXW23LFNZ2F633QMVXF6Y3MNFRWW#issuecomment-4294752612
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/4178/c4294752612 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20260422/60b043f6/attachment.htm>