From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Shall updaters fall back to other updaters?
Date: Thu, 30 Jun 2022 10:58:13 +0200 [thread overview]
Message-ID: <71902b16-4c29-c2f3-c99b-c103f3f6647c@crazy-compilers.com> (raw)
Hi,
while working on refreshing to a specific version (see
https://lists.gnu.org/archive/html/guix-devel/2022-06/msg00222.html) I
discovered that the updaters fall back to another updater. Is this intended?
Concrete example (using refresh to a specific version): Package "xlsxio"
has no version 0.2.30. When trying to refresh to this version, the
github updater comes first and of course fails to get this version. Then
the generic-git updater is triggered and tries to get the version.
IMHO each package should be handled by a single updater.
What do you think?
BTW 1: There are other packages which are handled be several updaters:
If you sum up the percent valued of "guix refresh --list-updaters" you
will get about 140%. Anyhow the generic-git updater contributed with
about 30% to this amount.
BTW 2: Which updater is used for each package is non-deterministic.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next reply other threads:[~2022-06-30 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 8:58 Hartmut Goebel [this message]
2022-06-30 9:10 ` Shall updaters fall back to other updaters? Maxime Devos
2022-07-01 13:15 ` Ludovic Courtès
2022-07-03 8:12 ` Hartmut Goebel
2022-07-03 15:11 ` Kaelyn
2022-07-04 12:33 ` Hartmut Goebel
2022-07-04 14:02 ` zimoun
2022-07-06 14:16 ` Ludovic Courtès
2022-07-06 16:24 ` zimoun
2022-07-18 11:15 ` Ludovic Courtès
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=71902b16-4c29-c2f3-c99b-c103f3f6647c@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--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).