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 |
Spread |
Newest |
Outdated |
Ignored |
|
tmux∗
|
41 |
2.830 |
2.711 2.66 2.56 2.42 2.4git20170318 2.39 2.23 2.14 2.04 1.9a4 1.92 1.86 1.72 1.64 1.52 1.42 1.3 1.2 1.1 1.0 0.9 0.8 |
9999 2.6.r93.gad417f6e 20190216-d5c8379 |
|
tmux-mem-cpu-load∗
|
8 |
3.4.06 |
2.2.1 |
9999 3.4.0.r10.g75b9ea7 |
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).