Ticket #17041 (new enhancement)
meaning of livecheck results should be made clearer
|Reported by:||devans@…||Owned by:||macports-tickets@…|
Using MacPorts installed from latest trunk:
port -d livecheck glibmm DEBUG: Port (livecheck) version is 2.18.1 DEBUG: Fetching http://freshmeat.net/projects-xml/glibmm/glibmm.xml DEBUG: The regex is "<latest_release_version>(.*)</latest_release_version>" DEBUG: The regex matched "<latest_release_version>2.14.2</latest_release_version>", extracted "2.14.2" glibmm seems to have been updated (port version: 2.18.1, new version: 2.14.2)
In this case, the current port version is 2.18.1 but freshmeat is not up to date and the latest version on record there is 2.14.2.
Livecheck assumes that the latest version from freshmeat is, in fact, the latest version of the port and declares it so after only checking to see that the freshmeat version is not equal to the port version.
In this case, I believe livecheck should check to see that the port version is greater than the freshmeat latest version and therefore the port seems to be up to date.
In otherwords, the highest version from the livecheck URL should be considered a new version only if it is greater than the port version.
Have only observed this when freshmeat is selected by default due to no explicit livecheck declarations as in glibmm but it occurs in several instances (freshmeat doesn't seem to be very good at keeping up to date). So can't say whether this faulty comparison occurs with any other livecheck URLs in similar circumstances.
- Summary changed from port livecheck using default freshmeat URL can make faulty version comparison to port livecheck makes faulty version comparison
- Milestone changed from MacPorts base bugs to MacPorts Future
comment:10 Changed 4 years ago by jmr@…
- Type changed from defect to enhancement
- Summary changed from port livecheck makes faulty version comparison to meaning of livecheck results should be made clearer