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.
7 project(s) on this page
| Project |
Spread |
Newest |
Outdated |
Ignored |
|
abiword∗
|
34 |
3.0.224 |
3.0.110 3.0.03 2.9.4 2.9.2svn20120213 2.8.64 2.8.1 2.6.82 2.4.5 2.4 |
20492.d5f731944 |
|
enchant∗
|
39 |
2.2.328 |
2.2.2 2.2.12 2.2.0 2.1.3 2.1.23 2.1.12 2.1.02 2.0.0 1.6.113 1.6.025 1.5.02 |
|
|
libwmf∗
|
32 |
0.2.12 |
0.2.10 0.2.8.432 |
|
|
mingw:enchant∗
|
2 |
1.6.02 |
|
|
|
mingw:enchant2∗
|
2 |
2.2.32 |
|
|
|
wv∗
|
31 |
1.2.924 |
1.2.7 1.2.48 |
|
|
wv2∗
|
16 |
0.4.214 |
0.3.1 0.2.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).