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 |
|
maxima∗
|
30 |
5.42.211 |
5.42.15 5.42.02 5.41.012 5.41-dev-20180615 5.40.04 5.39.02 5.38.14 5.37.2 5.36.12 5.35.1 5.34.1 5.33.0 5.32.1 5.29.1 5.24.0 5.23.2 5.14.0 5.9.3 |
5.42.1.279.ge2a275d4d |
|
maxima-ecl∗
|
1 |
5.42.2 |
5.39.0 |
|
|
maxima-sage∗
|
1 |
5.41.0 |
5.39.0 5.35.1 |
|
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).