From: Kaelyn <kaelyn.alexi@protonmail.com>
To: guix-devel <guix-devel@gnu.org>
Cc: "Hartmut Goebel" <h.goebel@crazy-compilers.com>,
"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Shall updaters fall back to other updaters?
Date: Sun, 03 Jul 2022 15:11:10 +0000 [thread overview]
Message-ID: <qYtZI3xjeElulZF3LKUiuwNcCsZu63Sau8YpoAhq-BwH7IRrijrIL6Aosz2V7bB1EQ0KNKxhSK_pNp641aIERM05dj-R1bIHgUncPHqo_M4=@protonmail.com> (raw)
In-Reply-To: <90e23ce1-00c6-a8b9-0362-313eaa1943d4@crazy-compilers.com>
------- Original Message -------
On Sunday, July 3rd, 2022 at 1:12 AM, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
> Am 01.07.22 um 15:15 schrieb Ludovic Courtès:
>
> > > 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?
>
>
> When looking at the code, I don't see any means of sorting:
> https://git.savannah.gnu.org/cgit/guix.git/tree/guix/upstream.scm#n245
>
> and below. (Maybe sorting is hidden in one of the function
> guile-internal used there there.)
I just looked at 'importer-modules and did some tracing of where the list of modules come from (back through 'all-modules, etc). It appears that by default the list of importer modules comes from 'scheme-file, which is defined at:
https://git.savannah.gnu.org/cgit/guix.git/tree/guix/discovery.scm#n43
That function builds a list of scheme files found recursively under a given directory with the help of 'scandir*. There is no sorting there or along the call chain back to 'importer-modules, so I'm fairly sure the directory entries are returned in a filesystem-dependent order. If the filesystem returns entries in sorted order or if the contents of that directory tree are relatively static (in that the order of directory entries hasn't changed), then the results will appear to be in a consistent/deterministic order. 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!
Cheers,
Kaelyn
next prev parent reply other threads:[~2022-07-03 15:11 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 [this message]
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='qYtZI3xjeElulZF3LKUiuwNcCsZu63Sau8YpoAhq-BwH7IRrijrIL6Aosz2V7bB1EQ0KNKxhSK_pNp641aIERM05dj-R1bIHgUncPHqo_M4=@protonmail.com' \
--to=kaelyn.alexi@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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).