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.
4 project(s) on this page
| Project |
Spr |
Newest |
Outdated |
Ignored |
Rank |
|
libopenmpt∗
|
16 |
0.5.15 |
0.5.06 0.4.115 0.4.6▲ 0.4.3▲ 0.3.19▲ 0.3.17▲ 0.3.9▲2 0.3.7▲2 0.3.6▲ 0.2.8760beta27▲ 0.2.7386beta20.3▲ |
0.5.r12741 2017-01-28-cf2390140 |
100.0 |
|
libopenmpt-modplug∗
|
2 |
0.8.9.02 |
|
|
94.11 |
|
mingw:libopenmpt∗
|
1 |
0.3.7 |
|
|
92.22 |
|
openmpt∗
|
6 |
1.29.02.002 1.29.2.0 1.29.2 |
1.29.1 1.29.01.00 1.29 1.28.9 1.23.5 1.23.4 1.22.5 |
|
84.81 |
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).
- vulnerable▲ - version is potentially vulnerable as there are related CVEs.