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
| Project |
Spr |
Newest |
Outdated |
Ignored |
|
mc∗
|
47 |
4.8.2335 |
4.8.2213 4.8.21.209 4.8.218 4.8.2010 4.8.198 4.8.186 4.8.17 4.8.162 4.8.152 4.8.142 4.8.132 4.8.12 4.8.112 4.8.10 4.8.8 4.8.7.180 4.8.72 4.8.4.159 4.8.1 4.7.0.4 4.7.0.23 4.6.3 4.6.2pre1 4.6.12 |
9999 4.8.16.r44.g51d0783 |
|
mcwin32∗
|
1 |
4.8.19 |
|
|
Legend:
- 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).