From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Parallel guix builds can trample?
Date: Tue, 18 Jan 2022 15:59:59 +0100 [thread overview]
Message-ID: <87wnixf5sg.fsf@gnu.org> (raw)
In-Reply-To: <7a2e92a6871fa2e40b749d8e4bfc6aa811df0a22.camel@telenet.be> (Maxime Devos's message of "Mon, 17 Jan 2022 18:44:19 +0100")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> Phil Beadling schreef op ma 17-01-2022 om 17:23 [+0000]:
>> For each build that is kicked off in quick succession the local cache
>> of the repo required updated by update-cached-checkout
>> * https://github.com/guix-
>> mirror/guix/blob/9f526f5dad5f4af69d158c50369e182305147f3b/guix/git.sc
>> m#L476
>> * https://github.com/guix-
>> mirror/guix/blob/9f526f5dad5f4af69d158c50369e182305147f3b/guix/git.sc
>> m#L279
>
>
> Maybe 'latest-repository-commit' and 'update-cached-checkout' commit
> can be modified to not use 'switch-to-ref', and instead directly ask
> libgit ‘what's the tree structure of commit cabba9e’ and call a
> procedure like 'add-file-tree-to-store'. That would avoid lock files,
> creating separate directories for concurrent checkouts, ...
That would be ideal. In Guix ‘write-file-tree’ already supports some
sort of virtual file systems, so it should be possible to use it to feed
the contents of the Git tree to the store.
Ludo’.
next prev parent reply other threads:[~2022-01-18 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 21:26 Parallel guix builds can trample? Phil
2022-01-11 23:16 ` Ricardo Wurmus
2022-01-12 7:00 ` Philip Beadling
2022-01-12 8:27 ` Ricardo Wurmus
2022-01-12 9:37 ` Phil
2022-01-17 17:23 ` Phil Beadling
2022-01-17 17:44 ` Maxime Devos
2022-01-18 9:28 ` Phil
2022-01-18 9:36 ` Maxime Devos
2022-01-18 14:59 ` Ludovic Courtès [this message]
2022-01-18 10:10 ` Phil
2022-01-18 12:53 ` Phil Beadling
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=87wnixf5sg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).