From: kiasoc5@disroot.org
To: guix-devel@gnu.org
Subject: Repology and outdated packages
Date: Tue, 07 Jun 2022 18:39:46 +0000 [thread overview]
Message-ID: <f563cd29cc2130f0aa54c2eeb139a5bddd8e98ff@disroot.org> (raw)
Dear Guix,
I've been watching the Repology page for Guix and I've noticed that we've dropped to 51% outdated packages [https://repology.org/repository/gnuguix]. We used to be at 40% outdated packages a few months ago.
I know that rolling release distros don't have to have the latest packages but this is not the best representation of Guix, especially when our friend NixOS claims they have the largest and most updated package collection [https://nixos.org/blog/announcements.html#nixos-22.05].
So without demanding more maintainer time, for now I just convince myself that:
- key toolchains such as Rust and Go are not always up to date, thus blocking the upgrade of several packages
- we package their dependencies separately (eg Rust crates, Go modules), these are a significant portion of Guix that cannot be constantly updated easily
- the Guix 1.4 release is coming soon so more time may be spent debugging that instead of updating the package archives
- the Guix branching model of staging/core-updates means we could say Guix is an LTS rolling release distro, which there aren't that many of
However I hope that faster package reviews can mean we stay updated faster without compromising package quality.
WDYT?
next reply other threads:[~2022-06-07 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 18:39 kiasoc5 [this message]
2022-06-07 18:47 ` Repology and outdated packages Nicolas Goaziou
2022-08-11 22:46 ` Vagrant Cascadian
2022-08-14 2:32 ` Maxim Cournoyer
2022-06-07 21:32 ` Maxime Devos
2022-06-09 8:02 ` Maxime Devos
2022-06-07 21:41 ` Maxime Devos
2022-06-08 21:38 ` Ludovic Courtès
2022-06-09 3:07 ` Oleg Pykhalov
2022-06-09 3:49 ` kiasoc5
2022-06-09 4:05 ` kiasoc5
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=f563cd29cc2130f0aa54c2eeb139a5bddd8e98ff@disroot.org \
--to=kiasoc5@disroot.org \
--cc=guix-devel@gnu.org \
/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).