Related projects are determined by recursively matching package homepage URLs. Note that this list may be incomplete as Repology may not be able to get homepage URLs from some repositories.
2 project(s) on this page
201905097 20190405 20190215 20190108 201812134 20181031 20180810 201806293 20180531 20180508 20180427 20180313 20180209 201801053 20170831 20170531 20170119 20161222 201609303 20160831 201605272 20160108 20150619 20150410 20141107 201409262 20140214 20130823 20130517 20100528 20080701 0.0_20130117
20190509 201902153 20181213 20181031 20180810 20180629 20180313 20171215 20170224 20161222 20160729 20160527 20100915 200904222 200901232 20081204
- Spread means how many repository families (e.g. all Debian versions are a single family) contain this package.
- newest#repos - newest known version. The number shows how many repository families have this version.
- devel - newest known devel (or unstable) version. There may be both devel and newest versions for a given package.
- unique - package is only present in a single repository family, there are no other sources to compare it against, so although it's latest version known to repology, is not really reliable.
- outdated - outdated version which requires updating.
- legacy - outdated version when a newer version is present. This is assumed to be legacy version preserved for e.g. compatibility.
- rolling - package is fetched from always latest snapshot or VCS master/trunk, so it is always latest and is not a subject for comparison.
- noscheme - the project does not have official versioning scheme, so versions used in repositories which are basically random.
- incorrect - version is known to be incorrect (e.g. version not officially released yet, or lacking alpha/beta/rc qualifier).
- untrusted - this source is known to likely supply incorrect versions, so is ignored proactively.
- ignored - version is ignored and excluded from comparison for some other reason (e.g. snapshots).