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 |
Spread |
Newest |
Outdated |
Ignored |
|
boehm-gc∗
|
40 |
8.0.417 |
8.0.27 8.0.0 7.6.122 7.6.102 7.6.85 7.6.64 7.6.48 7.6.05 7.4.18 7.4.16 7.4.14 7.4.12 7.4.10 7.4.42 7.4.27 7.2n 7.2m 7.2l 7.2k 7.2j 7.2g 7.2f 7.2e3 7.2d5 7.2c2 7.22 7.14 7.0 6.82 6.6 |
|
|
libatomic-ops∗
|
33 |
7.6.1019 |
7.6.88 7.6.67 7.6.43 7.6.22 7.4.6 7.4.46 7.4.24 7.4.0 7.4 7.3alpha3 7.2e 7.2alpha5.cvs20101124 7.2alpha4 1.22 |
|
|
mingw-w64-gc∗
|
1 |
8.0.2 |
|
|
|
mingw-w64-libatomic-ops∗
|
1 |
7.6.10 |
|
|
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).