[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)

As an alternative approach, we could also just have the pre-release name in the cmake config, alongside the version number itself (and concatenate the two automatically).

The advantage is that, for production builds, the version would be static (no need to parse or generate anything). It would only be dynamic for development builds where we want that gitcount suffix, and even that's only if we really want that suffix in the version string itself (as opposed to just the tarball name).

The disadvantage is that the git tag (the pre-release part) would be duplicated in the cmake config and thus remembered to be "bumped". But that's what we always did, just through the awkward numbering scheme.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4178#issuecomment-4258680521
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/4178/c4258680521 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20260416/f08ddb07/attachment-0001.htm>