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 |
|
tmux∗
|
46 |
3.1~rc1 3.1rc1 3.0a26 |
3.0.1 3.02 3.0_a2 3.0.a 2.9a7 2.95 2.88 2.79 2.65 2.53 2.4 2.4git20170318 2.39 2.22 2.13 2.02 1.9a3 1.9 1.85 1.7 1.63 1.5 1.4 |
9999 8107_3.0a.r184.g745233d6 20200102-7110226 |
|
tmux-mem-cpu-load∗
|
9 |
3.4.08 |
2.2.1 |
9999 3.4.0.r10.g75b9ea7 |
|
tmux-ver-28∗
|
1 |
2.8 |
|
|
|
tmux-xdg∗
|
1 |
|
|
2.8.r292.g78adc263 |
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).