[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Shall updaters fall back to other updaters?
From: |
Ludovic Courtès |
Subject: |
Re: Shall updaters fall back to other updaters? |
Date: |
Fri, 01 Jul 2022 15:15:53 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) |
Hello,
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> 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?
Yes.
> 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.
I agree with Maxime: trying out several updaters is the right one.
> 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.
Heh, true. :-)
> BTW 2: Which updater is used for each package is non-deterministic.
Do you have an example? I’d think they’re always tried in the same
order, no?
Thanks,
Ludo’.
- Re: Shall updaters fall back to other updaters?,
Ludovic Courtès <=