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 |
|
dummy∗
|
1 |
0.2 |
|
|
|
zsh∗
|
46 |
5.7.137 |
5.7 5.6.211 5.6.1 5.62 5.5.16 5.53 5.4.24 5.4.12 5.3.19 5.32 5.24 5.1.12 5.1 5.0.8 5.0.73 5.0.6 5.0.54 5.0.4 5.0.24 5.0.1 4.3.172 4.3.15 4.3.14 4.3.122 4.3.113 4.3.10 |
9999 5.2.r502.ge35dcae scm |
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).