[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Shall updaters fall back to other updaters?
From: |
Hartmut Goebel |
Subject: |
Shall updaters fall back to other updaters? |
Date: |
Thu, 30 Jun 2022 10:58:13 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 |
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 |
- Shall updaters fall back to other updaters?,
Hartmut Goebel <=