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
|| 1.0.92 1.0.85 1.0.72
|| 9999 184.108.40.206.gba5db4d 1.1.0+qtbuild
|| 3.11.0+git20220731.1.ef0cb1a 3.11.09 3.10.21-1 3.10.217 3.10.20 3.10.19 3.10.175 3.10.162 3.10.15 3.10.132 3.10.11 3.10.9 3.10.73 3.10.5 3.10.2 3.10.1 3.10.0 3.9.6 3.9.3 3.9.1 3.9.02 3.8.2 3.5.22 3.2.0 2.20.3 0.11.0
|| 3.10.21 3.10.17_git20210307
- Spread means how many repository families (e.g. all Debian versions as well as Ubuntu and other derivatives make 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 the 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).
- vulnerable▲ - version is potentially vulnerable as there are related CVEs.