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 |
|
brotli∗
|
39 |
1.0.734 |
1.0.63 1.0.52 1.0.43 1.0.33 1.0.22 1.0.1 1.0 0.6.02 0.5.23 0.3.0 0.1-1.e992cce 0.1.0~git30 |
9999 1.0.7.r5.g4b2b2d4 r49.e992cce 20190901 1.0.7.20190901 1.0.7_2 |
|
mingw:brotli∗
|
2 |
1.0.72 |
|
|
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).