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 |
|
aom∗
|
24 |
1.0.0.errata13 1.0.0-errata12 |
1.0.014 1.0.0.r2236.g0233da474 |
9999 1.0.0.r1028.g78e6b2cb84 1.0.0.20190906 1.0.0.20190901 1.0.0.2774 1.0.0.2072 1.0.0.12 1.0.0-errata1-0.22b150b |
|
mingw:aom∗
|
1 |
1.0.0 |
|
|
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).