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 |
|
axel∗
|
32 |
2.17.617 |
2.17.52 2.17.3 2.16.1-1 2.16.18 2.16 2.152 2.14.1 2.13.1 2.124 2.52 2.4.1 2.410 2.3 |
9999 |
|
cycfx2prog∗
|
2 |
0.472 |
|
|
|
elinks∗
|
35 |
0.12pre610 0.12_pre6 0.11.77 |
0.12pre5 0.11.5 git20131231 |
9999 0.13.1481.rf86be659 scm 201706132 20160207 0.13.4008.f86be659 0.13~0.20190723 0.133 0.133 0.13_pre_pre20180225 0.13.GIT 0.12.3.2 0.12 0.125 0.12rc6 0.11.996 |
|
elinks-small∗
|
1 |
0.12pre6 |
|
|
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).