Tracking package updates with release-monitoring.org

Posted Jan 25, 2017 17:17 UTC (Wed) by ScottMinster (subscriber, #67541)
Parent article: Tracking package updates with release-monitoring.org

Two million packages? I figured that would mean a lot of overlap in functionality, but it looks like there's even a lot of plain duplicates. As an example, I searched for ImageMagick and found 722 hits! Sure, you'd expect variations like IM wrapper for Perl, Python, etc, but there were 195 Node.js (npm) hits and 339 Go hits. Many of them appeared to be github forks of one another. At least a number of the npm hits appear to be different wrappers (duplicate functionality if not code) or projects that use ImageMagick.

It's clear to me at least that there is still is value in having a distribution comb through all of that to find the "right" version of the library. Having a high absolute count is not really desirable if they are all duplicates.