unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: rchar01 <rchar01@protonmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Comparing Guix packages list with other distributions
Date: Wed, 11 Jul 2018 07:34:39 +0200	[thread overview]
Message-ID: <20180711073439.2563f94a@alma-ubu> (raw)
In-Reply-To: <OdgSG5CThuHUSHCm8eP_DcVeSdCN-626_6hUZ0FpeDjfJ0snCB-sjFZySGNqoX1YUpzHcm2fLeHayuPM1ALupn6JGsy3fuKm_VQNrpk5zQU=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]

On Tue, 10 Jul 2018 14:29:49 -0400
rchar01 <rchar01@protonmail.com> wrote:

> I was looking for a way to compare Guix packages (versions, quantity)
> with other distributions and found a simple solution:
> https://repology.org/ https://github.com/repology/repology
> 
> Best,
> Robert

Hi Robert,

thanks for bringing attention back to this nice site! ng0 already
mentioned it a while ago and I'm looking at it from time to time.

Here is the overview page for Guix with some statistics and graphs:

https://repology.org/repository/gnuguix

Note the slowly degration in the graph as other distros update their
packages. Then we have a rapid step up, caused by either
core-updates/staging-merges or updating of the websites package list.

And this is the list of outdated Packages (Much work to pick
from :-) ):

https://repology.org/metapackages/?inrepo=gnuguix&outdated=1


Currently, the site says we have 2494 out of 7855 packages outdated, so
about a quarter of our packages are outdated. Repology doesn't check the
upstream sites, so outdatedness in Repology is always relative to the
other distros. There could be even more work.

From the overview page, there is also a link to a problems page:

https://repology.org/repository/gnuguix/problems

We have 914 "problems". Recently that was at about 300. The problems are
mainly redirects http->https, some dead sites or 404-errors. The big
jump with about 600 new problems came due to the closing of CPAN search
engine, now you should use MetaCPAN.

There is also a REST API for Repology. One could even write a
"checker"/updater for Guix, though I wasn't sure how it would fit into
the zoo of (language-)specialized updaters Guix has.

Finally Repology has some rules to fit package names of different
distributions together to socalled "metapackages":

https://github.com/repology/repology-rules

Whenever there are packages in Guix that do not compare to those of
others distros, one could offer a pull-request against the
rules-sourcecode-repository.

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      parent reply	other threads:[~2018-07-11  5:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 18:29 Comparing Guix packages list with other distributions rchar01
2018-07-10 22:47 ` Pierre Neidhardt
2018-07-11  5:34 ` Björn Höfling [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180711073439.2563f94a@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@gnu.org \
    --cc=rchar01@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).