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
| Metapackage |
Spread |
Newest |
Outdated |
Ignored |
|
aspcud∗
|
8 |
1.9.47 |
1.9.13 1.9.0 1.8.0 |
r8385 2011.03.17 |
|
clasp∗
|
7 |
3.3.44 |
3.3.3 3.3.2 3.2.12 3.1.42 3.1.32 3.1.0 2.1.4 2.0.4 0.8.99.20181128 |
|
|
clingo∗
|
4 |
5.3.04 |
5.1.0 |
|
|
gringo∗
|
7 |
5.3.02 |
5.2.3 5.2.2 5.1.0 4.5.46 4.4.0 4.2.1 3.0.3 |
|
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).