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.
5 project(s) on this page
| Project |
Spr |
Newest |
Outdated |
Ignored |
|
bdwgc∗
|
3 |
8.0.43 |
|
|
|
boehm-gc∗
|
45 |
8.0.438 |
7.6.122 7.6.84 7.6.62 7.6.47 7.6.06 7.4.4 7.4.25 7.2e 7.2d4 7.2c 7.2▲ 7.1▲4 7.0▲ 6.8▲ 6.6▲ |
|
|
libatomic-ops∗
|
37 |
7.6.1032 |
7.6.8 7.6.66 7.6.43 7.6.23 7.4.8 7.4.6 7.4.44 7.4.23 7.4.0 7.4 7.3 7.2e 7.2.e 7.2alpha5.cvs20101124 7.2alpha4 1.22 |
|
|
mingw:gc∗
|
2 |
8.0.4 |
7.6.4 |
|
|
mingw:libatomic-ops∗
|
2 |
7.6.10 |
7.6.4 |
|
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).
- vulnerable▲ - version is potentially vulnerable as there are related CVEs.