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 |
|
amarok∗
|
19 |
2.9.09 |
2.9.0.r367.fc370bbebf 2.9.0.r264.g1a25008915 2.8.904 2.8.08 2.6.0 2.5.96 2.5.0 2.0.2 |
2.9.0.r230.ged38fe752f scm 2.9.20190508 2.9.70_pre20190111 2.9.0-20180618 2.9.0.277 |
|
mingw:taglib∗
|
1 |
1.11.1 |
|
|
|
taglib∗
|
39 |
1.11.136 |
1.114 1.102 1.10beta 1.9.16 1.9 1.82 1.7.22 1.72 1.6.12 1.5-svn |
v1.11.1.r152.6455671e 1.11.1_p20181028 |
|
taglib-extras∗
|
21 |
1.0.121 |
|
|
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).