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 |
Spr |
Newest |
Outdated |
Ignored |
Rank |
|
libjpeg-turbo∗
|
50 |
3.0.024 |
2.1.5.114 2.1.53 2.1.4+git20221121.1.74d5b16 2.1.413 2.1.37 2.1.29 2.1.13 2.1.04 2.0.90▲3 2.0.8▲ 2.0.7▲ 2.0.6▲7 2.0.5▲5 2.0.4▲4 2.0.3▲ 2.0.2▲2 2.0.1▲ 2.0.0▲4 1.5.3▲8 1.5.2.6▲ 1.5.2▲2 1.5.1▲3 1.5.0▲2 1.4.2▲ 1.4.0▲ 1.3.1▲2 1.3.0▲2 1.2.90▲3 1.2.1.201304081▲ 1.2.1▲2 |
2.1.3.r16.g290ddbf7 HEAD |
100.0 |
|
jpeg-compat∗
|
1 |
2.0.6 |
|
|
94.91 |
|
libjpeg-turbo.gcc∗
|
1 |
3.0.0 |
2.1.5.1 2.1.5 2.1.4 2.1.3 2.1.1 |
|
92.22 |
|
libjpeg-turbo.vc∗
|
1 |
3.0.0 |
2.1.5.1 2.1.5 2.1.4 2.1.3 2.1.2 2.1.1 |
|
92.22 |
Legend:
- 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.