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.

**3** project(s) on this page

Metapackage | Spread | Newest | Outdated | Ignored |
---|---|---|---|---|

0ad∗ | 24 |
alpha 23b^{13} |
alpha 23^{11} alpha 22^{6} alpha 21^{9} alpha 20^{3} alpha 19 alpha 18 alpha 17^{2} alpha 16^{3} alpha 15^{2} alpha 14 alpha 11 |
21551 0.0.23.1^{2} 0r11339 |

0ad-data∗ | 16 |
alpha 23b^{11} |
alpha 23^{6} alpha 22^{5} alpha 21^{7} alpha 20^{2} alpha 17 alpha 16^{2} alpha 15 alpha 11 |
0.0.23.1 0r11339 |

0ad-zh-lang∗ | 1 |
0.0.19 |

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).