Repology analyzes multiple package repositories and compares versions of a packages in them.
The report it produces shows which repositories contain or lack which packages, and whether packages need updating.
- For users:
- Compare completeness and freshness of package repositories, choose most up to date distro
- Find out what repositories contain newest versions of packages you need
- For package/port maintainers:
- Another way to track new releases of software you package
- Compete with other distros in keeping up to date
- Find fellow maintainers to resolve packaging problems together
- Keep package naming and versioning schemes in sync to other repos for your and your user's convenience
- For software authors:
- Keep track of how well your project is packaged
- Keep in touch with your product package maintainers
Repology is currently in an early phase of development, with a goal of creating usable utility in a quick and dirty way. For now, it is usable in two modes: as a command line generator of single HTML report and a static website generator for this website.
BEWARE that this website is in beta state. Expect links and bookmarks to it to become broken at any moment
Since different repositories use different package naming and versioning schemes, repology transforms package names to aggregate information on single package in a single entity, and transforms versions to be comparable. So expect packages names in repology to be different from ones in your repository. Name transformation is controlled by a ruleset, which you may need to extend if you find a mismatched package. Read more
Repology generates a table with rows corresponding to packages and columns corresponding to repositories. Cells contain color-coded versions of each package in each repo. Colors have following meanings:
- 1.2.3 - package is at latest version among all repos. It's likely up to date.
- 1.2.3 - some other repository contain newer version of this package. It may need updating.
- 1.2.32 - there are multiple packages with the same name in this repository, and one of the is at latest version, but others are not. It may indicate one of the following conditions:
- There are unrelated packages with the same name (for example, clementine may be either X11 window manager, or music player, unrelated projects). The package should be split with renaming rule.
- There are packages for legacy versions (e.g. Qt version 4 and 5). One of them has to be on older version, everything is fine.
- There are multiple flavors of the same package (for example, Russian and French l10n packages for libreoffice) and some of them are outdated.
- 1.2.3 - package version is ignored. This may indicate that a specific repo uses broken versioning scheme which makes it impossible to compare it with other repos. Package or repository policy may require fixing.
- 1.2.3 - package is present only in one repository, there's nothing to compare it to. This may mean a not-so-popular package which haven't made it into other repos yet, or an unique naming scheme, which may require a rule to be merged with differently named packages in other repos. This may be a package unique to specific repository either (e.g. FreeBSD-specific software in FreeBSD ports).
The repository data and the website are updated hourly.
Junior tasks include proofreading English texts (README, html templates), finding more mismatched packages and adding name transformation rules for them.