search

repology / repology-rules

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

Merge ldid (from ProcursusTeam) #786

Closed TheRealKeto closed 6 months ago

TheRealKeto commented 6 months ago

The Procursus Team maintains a fork of an original project named ldid as ldid-procursus. In Repology, some entries within the ldid project aim to the version scheme used by the Procursus Team (causing them to appear to be outdated).

Instead, these entries (notably from the AUR), now or in the future (from other package managers), are to be considered part of the ldid-procursus project.

AMDmi3 commented 6 months ago

Is the original project still maintained? At least its repo looks dead.

The change is not correct, as such rule belongs to 850 ruleset and requires counterpart to match the original project and a fallback. However it looks like in this case it would make more sense to instead merge into a single project and make procursus versions compare higher than original.

TheRealKeto commented 6 months ago

Thanks for the feedback!

In regards to the original project vs the one maintained by the Procursus Team, a rationale behind the projects existing with different names comes from a comment on a pull request submitted to replace the original project with the aforementioned fork on Homebrew.

In other words, the original project (ldid) is still maintained, rather than abandoned, so the best case is to keep the packages separate. Unsure if this is applicable to Repology, so the approach is entirely up to you.

AMDmi3 commented 6 months ago

I don't see any evidence that the original project is maintained. On the contrary, there were no releases since 2021, original git repository is not accessible, and, if the mentioned comment is correct, author does not accept patches. So I'd prefer to merge it instead (and procursus versions will now be compared greater that original ones), we can split it anytime if there are reasons for that.