Metapackages

5 item(s) on this page

Metapackage	By gurkan@phys.ethz.ch	Spread	Newest	Outdated	Ignored
gnustep-examples∗	1.4.0 1.3.0 1.2.0	6	1.4.03	1.3.02
gnustep-gorm∗	1.2.24 1.2.23 1.2.20 1.2.16 1.2.10	11	1.2.242	1.2.235 1.2.202 1.2.12 1.2.1
gnustep-make∗	2.7.0 2.6.8 2.6.6 2.6.2 2.6.1	24	2.7.015	2.6.83 2.6.72 2.6.63 2.6.2 2.6.0 2.4.0
gnustep-projectcenter∗	0.6.2 0.6.1 0.6.0	10	0.6.28	0.6.0
gnustep-projectmanager∗	0.2	2	0.2

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).