From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Kaelyn <kaelyn.alexi@protonmail.com>, guix-devel <guix-devel@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Shall updaters fall back to other updaters?
Date: Mon, 4 Jul 2022 14:33:04 +0200 [thread overview]
Message-ID: <9a68beb7-50f0-9998-9daf-2b036a8e9e66@crazy-compilers.com> (raw)
In-Reply-To: <qYtZI3xjeElulZF3LKUiuwNcCsZu63Sau8YpoAhq-BwH7IRrijrIL6Aosz2V7bB1EQ0KNKxhSK_pNp641aIERM05dj-R1bIHgUncPHqo_M4=@protonmail.com>
Am 03.07.22 um 17:11 schrieb Kaelyn:
> To me, this feels like the importers will need a more deterministic order imposed on them to get import results that are consistent across systems. HTH!
Many thanks for your analysis.
Meanwhile it came to my mind that I actually have different
installations of guix which I can compare, Below are three
installations. each one has a different order (these are actually
different versions of guix with different importers/updaters, anyhow the
order should be the same):
stackage pypi opam minetest launchpad kde hexpm hackage gnome github
generic-git gem elpa egg crate bioconductor cran cpan savannah
generic-html gnu-ftp sourceforge xorg kernel.org gnu
stackage pypi opam minetest launchpad kde hackage gnome github
generic-git gem elpa egg crate cran bioconductor cpan kernel.org
sourceforge gnu generic-html gnu-ftp xorg savannah
stackage pypi opam minetest launchpad kde hackage gnome github
generic-git gem elpa egg crate bioconductor cran cpan sourceforge
generic-html gnu-ftp savannah xorg kernel.org gnu
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2022-07-04 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 8:58 Shall updaters fall back to other updaters? Hartmut Goebel
2022-06-30 9:10 ` 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 [this message]
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=9a68beb7-50f0-9998-9daf-2b036a8e9e66@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=kaelyn.alexi@protonmail.com \
--cc=ludo@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).