search

repology / repology-rules

Package normalization ruleset for Repology
https://repology.org
GNU General Public License v3.0
106 stars 124 forks source link

Better handling of ncurses versioning? #780

Closed jon-turney closed 7 months ago

jon-turney commented 7 months ago

Looking at the list of versions on https://repology.org/project/ncurses/information is not as helpful as it might be.

I'm told that upstream releases e.g. 6.4 and then a sequence of 6.4-YYYYMMDD "snapshots". These are the things that everyone is packaging. Unfortunately, distro handling of these is inconsistent, which is perhaps not helped by the '-' character not being allowed in versions in some (many?) places.

I think maybe a rule transforming (\d+).(\d+)[_-+]p?(\d+) to \1.\2.\3 or something like that might be appropriate?

Observed behavior

Repology tells me that 6.4 is the latest version

Expected behavior

Repology tells me that (currently) 6.4.20240127 is the latest version

AMDmi3 commented 7 months ago

Unfortunately, distro handling of these is inconsistent, which is perhaps not helped by the '-' character not being allowed in versions in some (many?) places

There's no problem here as repology treats e.g. 6.4.20240127, 6.4-20240127, 6.4_20240127 and 6.4+20240127 equally.

Repology tells me that (currently) 6.4.20240127 is the latest version

I'll mark three component versions as devel. That way 6.4 would remain as latest, and latest snapshot would be classified as devel.