https://bugs.kde.org/show_bug.cgi?id=389864
Bug ID: 389864 Summary: git tagging issues Product: konsole Version: master Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- This has come up before (and corrected, after a code review) but since Konsole isn't the only application concerned I'm logging a ticket for it: I maintain a semi-official MacPorts packaging tree for quite a few KF5 projects, and a considerable number of those ports (packages) are based on snapshots taken from the project git repos - if possible the master branch. I rely on `git describe` to get a representative versioning for those ports. Where necessary I add git tags myself, but it would be great if the upstream version tags could be set in such a way that the `git describe` returns a sensical value for the master branch too. That is: something in the form YY.MM.NN-commitNr which: - increases monotonically - ideally corresponds to or reflects the current stable release - at least corresponds to the version reported by `foo --version` and the KAbout data. This tends to work well enough for most projects, but for some like konsole that has not been the case for a while now: - `git describe` returns v17.11.90-110-ge2184aef on the master branch - it returns v17.12.1-2-g5f0eea61 on the 17.12 release branch - `konsole --version` returns 18.03.70 For comparison, okular's git log shows this: ``` commit e7f90332eaff404fbe03be814c94b5c4625542e2 Author: Albert Astals Cid <aa...@kde.org> Date: Thu Jan 4 18:50:10 2018 +0100 GIT_SILENT Upgrade KDE Applications version to 17.12.1. ``` (though apparently the 17.12.1 tag was set in commit 6ed35fcca3950a54dd5dbd80b90ecd7761467692) -- You are receiving this mail because: You are watching all bug changes.