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 |
|
squid∗
|
34 |
4.614 3.5.286 |
4.56 4.46 4.2 4.1 4.0.25 4.0.24 4.0.232 4.0.21 4.0.20 3.5.278 3.5.262 3.5.25 3.5.24 3.5.23 3.5.222 3.5.21 3.5.202 3.5.19 3.5.12 3.4.142 3.4.82 3.4.6 3.4.2 3.3.82 3.1.233 3.1.19 3.0.STABLE16 2.7.STABLE92 |
4.1 5.0.0 |
|
squid-langpack∗
|
1 |
20190110 |
20170901 20150704 20140506 20121005 20111114 |
|
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).