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.
2 project(s) on this page
|| 2.49.9211 2.49-92 2.4917
|| HEAD clisp.126.96.36.1997.06.25.r576.g129eaf3f1 2.50_20220927_acb1266ee 2.50_20191103_c26de78732 2.50.0-20230719 2.50 2.503 2.50.0 2.50pre20230112 2.50pre20171114 2.49.20230112.git4d251c6 2.49.20210628.gitde01f0f 2.49.20180218+really2.49.92 2.49.20170913 2.49.93 2.49.935 2.49.93+
|| 2.28 2.16 1.132 1.10+cvs20100619 1.106
- 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.