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
| Project |
Spread |
Newest |
Outdated |
Ignored |
|
arma∗
|
1 |
4.400 |
|
|
|
armadillo∗
|
18 |
9.400_RC1 9.300.28 |
9.200.8 9.200.73 9.200.6 9.200.5 9.100.53 8.600.1 8.400.02 8.300.2 8.300.0 8.100.0 7.960.1 7.900.1 7.600.2 7.500.0 7.300.1 6.700.7 6.500.5 4.550.2 4.450.2 4.200.0 2.4.2 |
2019-04-16-f00d3225 |
|
mingw-w64-armadillo∗
|
1 |
8.400.0 |
|
|
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).