From: Ricardo Wurmus <rekado@elephly.net>
To: Philip Beadling <phil@beadling.co.uk>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Parallel guix builds can trample?
Date: Wed, 12 Jan 2022 09:27:21 +0100 [thread overview]
Message-ID: <87r19d5pcw.fsf@elephly.net> (raw)
In-Reply-To: <LO0P265MB594168298E99C9A2D880E4B1F9529@LO0P265MB5941.GBRP265.PROD.OUTLOOK.COM>
Philip Beadling <phil@beadling.co.uk> writes:
> The source in each one will be slightly different and although I only
> specify commit id in the package
How are you using Guix with this? Do you generate Guix package
expressions? Do you use “guix build --with-commit”?
If the hash in the “source” field corresponds to source code in the
store then it doesn’t matter what the commit id or version string says.
The hash identifies the source.
--
Ricardo
next prev parent reply other threads:[~2022-01-12 8:32 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 [this message]
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
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=87r19d5pcw.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=phil@beadling.co.uk \
/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).