repology-rules
repology-rules copied to clipboard
Handle _git and related versions on Alpine Linux as more recent than unsuffixed
From APKBUILD Reference#pkgver (emphasis on relevant part mine):
A Suffix suf in the above format can be one of the following to indicate that the release is less recent than the version without the suffix: alpha, beta, pre, rc [5] These are for indicating more recent releases: cvs, svn, git, hg, p [6] All other suffices are invalid. To package a specific git commit, the date of the commit gets appended to the latest release, e.g. 1.0.0_git20180204.
Note that pkgvers where the version is "0" (0_git202xxxxx, etc.) are for packages that don't have any tagged releases. If there's a tagged release in some other repository, then this is pretty much guaranteed to be older.
Some random examples of affected packages:
- https://repology.org/project/gnomecast/versions
- https://repology.org/project/dvtm/versions
- https://repology.org/project/cpuburn/versions
- https://repology.org/project/dolphin-emu/versions
(The only real exception here is https://repology.org/project/clementine-player/versions, since 1.4.0 isn't yet a real release (and seeing upstream activity, likely won't be for a while...) - that's a mistake on my part (I'm the maintainer of the package), and clearly bending the rules I mentioned here, and I'll see if I can fix this upstream.)
This also applies to postmarketOS: https://repology.org/project/abootimg/versions
+1 A more proper solution would be marking all _git packages as rolling.
From what I can see, these are not rolling. These have checksums recorded, so they are from fixed point in time, and the version suggests which release they are based on. It should be handled like normal snapshot versions. They already are, what's missing is a flag to handled them as post-release, and handle them similarly for postmarketos.