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 |
|
appdata-tools∗
|
10 |
0.1.88 |
0.1.75 |
|
|
appstream-data∗
|
5 |
20181212 |
30 29 28 27 26 17 72 |
|
|
appstream-glib∗
|
27 |
0.7.1513 |
0.7.1411 0.7.13 0.7.12 0.7.11 0.7.92 0.7.82 0.7.73 0.7.62 0.7.2 0.7.1 0.7.0 0.6.133 0.6.11 0.6.10 0.6.8 0.6.32 0.5.17 0.5.13 0.5.11 0.5.0 0.4.1 0.3.62 0.3.4 0.3.0 0.2.5 |
0.6.4.r26.gb6d6c23 |
|
qqwing∗
|
20 |
1.3.420 |
1.3.3 1.3.2 |
|
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).