Vertical badge
This badge shows versions and up to date status of this project in all known repositories.
Markdown code:
[![Packaging status](https://repology.org/badge/vertical-allrepos/libgccjit.svg)](https://repology.org/project/libgccjit/versions)
HTML code:
<a href="https://repology.org/project/libgccjit/versions"> <img src="https://repology.org/badge/vertical-allrepos/libgccjit.svg" alt="Packaging status"> </a>
HTML code for right-aligned badge (most useful for README.md as it allows other content to flow around it not leading to space waste):
<a href="https://repology.org/project/libgccjit/versions"> <img src="https://repology.org/badge/vertical-allrepos/libgccjit.svg" alt="Packaging status" align="right"> </a>
May be tweaked with header
, minversion
, and allow_ignored
parameters (see below).
It's also possible to specify number of columns with columns=<N>
parameter.
You may exclude specific kinds of sources (repository
, modules
, site
) with exclude_sources
parameter. E.g. use exclude_sources=modules,site
to exclude e.g. PyPI and Wikidata.
You may also exclude old and no longer supported repositories with exclude_unsupported=1
parameter. Note however that this will only work for repositories which have end of life date (valid_till
) set in the configs. Feel free to submit PRs with missing dates.
Tiny badge with number of repositories
This shows total number of repository families featuring this package. Repository family is an aggregation of related repositories, e.g. Debian Stable, Testing, Unstable and Experimental all belong to a single family and are thus only counted once.
Markdown code:
[![Packaging status](https://repology.org/badge/tiny-repos/libgccjit.svg)](https://repology.org/project/libgccjit/versions)
HTML code:
<a href="https://repology.org/project/libgccjit/versions"> <img src="https://repology.org/badge/tiny-repos/libgccjit.svg" alt="Packaging status"> </a>
May be tweaked with header
parameter (see below).
Tiny badge with latest packaged version(s)
This shows latest version(s) known to repology. There may be multiple versions, for example devel and newest, or multiple variations of the same version encountered in some repositories (e.g.1.0.0
and 1.0
). These badges also support minversion=
parameter.
Markdown code:
[![latest packaged version(s)](https://repology.org/badge/latest-versions/libgccjit.svg)](https://repology.org/project/libgccjit/versions)
HTML code:
<a href="https://repology.org/project/libgccjit/versions"> <img src="https://repology.org/badge/latest-versions/libgccjit.svg" alt="latest packaged version(s)"> </a>
May be tweaked with header
parameter (see below).
Tiny per-repository badges with version
These show version in specific repository. Pick as many as you want! You may add ?header=
to the URL to leave only the version.
May be tweaked with header
, minversion
, and allow_ignored
parameters (see below).
Additional parameters
Most badges may be tweaked by specifying additional parameters in the URL.
header
Works for all badges. Changes the header/caption of the badge. Specify empty header to remove it completely.
https://repology.org/badge/version-for-repo/gnuguix/libgccjit.svg |
|
https://repology.org/badge/version-for-repo/gnuguix/libgccjit.svg?header= |
|
https://repology.org/badge/version-for-repo/gnuguix/libgccjit.svg?header=PACKAGE |
minversion
Specify "minimal acceptable version" - any versions lesser than it will be marked with crimson color. Useful to mark unacceptable versions based on arbitrary criteria, for instance unsupported dependency versions.
https://repology.org/badge/version-for-repo/gnuguix/libgccjit.svg |
|
https://repology.org/badge/version-for-repo/gnuguix/libgccjit.svg?minversion=999999999 |
allow_ignored
By default, when picking the version to show on badge, all rolling, noscheme, incorrect, untrusted, ignored versions are skipped (so, for instance, rolling 9999
versions in Gentoo do not hide real stable versions). When allow_ignored
parameter is specified (with some non-empty value), the greatest version is always picked regardless of status.
https://repology.org/badge/version-for-repo/gnuguix/libgccjit.svg?allow_ignored=1