From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Richard Sent <richard@freakingpenguin.com>
Cc: Mauritz Stenek <mstenek@disroot.org>, help-guix@gnu.org
Subject: Re: Replication question
Date: Wed, 17 Apr 2024 18:08:02 +0200 [thread overview]
Message-ID: <87frvkotul.fsf@pelzflorian.de> (raw)
In-Reply-To: <87frvlci8w.fsf@freakingpenguin.com> (Richard Sent's message of "Tue, 16 Apr 2024 13:47:11 -0400")
Hello Richard; yours is a good answer. Let me add:
Richard Sent <richard@freakingpenguin.com> writes:
> 1. Guix time-machine. e.g.
> guix time-machine --commit=XXX -- package -m manifest.scm
>
> a. This will create a profile containing the exact packages at that
> moment in time, including A@old.
>
> b. All packages will be at whatever version the corresponding
> Scheme package variable is at for that commit. See (info "(guix)
> Invoking guix time-machine"). Probably not the best idea to use
> long term.
Note that “guix time-machine … -- install” or “guix time-machine … --
build” can be used for individual packages. So repeated time-machine to
each package’s commit can reproduce the environment (have not tested it,
but should be true).
guix time-machine can also take a channel description file instead
of a commit, if we are talking about other channels.
Also to comment on Mauritz’ question, the @ syntax of guile@2.2.7 has
nothing to do with reproducibility. Everybody understood correctly that
by A@old, A from an old Guix commit was your intended meaning; I want to
clarify this for future readers.
Regards,
Florian
prev parent reply other threads:[~2024-04-17 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 16:26 Replication question Mauritz Stenek
2024-04-16 16:41 ` Felix Lechner via
2024-04-16 17:47 ` Richard Sent
2024-04-17 16:08 ` pelzflorian (Florian Pelz) [this message]
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=87frvkotul.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=help-guix@gnu.org \
--cc=mstenek@disroot.org \
--cc=richard@freakingpenguin.com \
/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.
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).