From: Simon Tournier <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, guix-devel <guix-devel@gnu.org>
Cc: Christopher Baines <guix@cbaines.net>
Subject: Re: Building and caching old Guix derivations for a faster time machine
Date: Thu, 16 Nov 2023 10:59:21 +0100 [thread overview]
Message-ID: <86h6lmvx1i.fsf@gmail.com> (raw)
In-Reply-To: <87o7g29c94.fsf@elephly.net>
Hi Ricardo,
On Fri, 10 Nov 2023 at 10:29, Ricardo Wurmus <rekado@elephly.net> wrote:
> to me the biggest downside of using “guix time-machine” is that it has
> to do a lot of boring work before the interesting work begins. The
> boring work includes building Guix derivations for the given channels,
> most of which have long been collected as garbage on ci.guix.gnu.org.
>
> It would be helpful, I think, to more aggressively cache these
> derivations and their outputs, and to go back in time and build the
> derivatinons for past revisions of Guix. I would expect there to be a
> lot of overlap in the produced files, so perhaps it won’t cost all that
> much in terms of storage.
I agree. And it rings a bell about a discussion on the private
guix-sysadmin mailing list, subject: Backup for substitutes.
Back in 2022, Alexandre from Univ. Montpellier was proposing to store
the artifacts the project would like to keep for a longer term. Well, I
do not know what is the current status.
That’s said, I am in favor:
1. keep all the derivations and their outputs required by Guix itself.
2. keep all the outputs for some specific revisions; say v1.0, v1.1,
v1.2, v1.3, v1.4, and some other chosen points in time.
About #1, it will help when running “guix time-machine”. About #2, it
will help with concrete issues as time-bombs when running “guix
time-machine -- shell”
The questions are: which server? who maintain? :-)
Cheers,
simon
next prev parent reply other threads:[~2023-11-16 10:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 9:29 Building and caching old Guix derivations for a faster time machine Ricardo Wurmus
2023-11-16 9:59 ` Simon Tournier [this message]
2023-11-16 15:39 ` Ludovic Courtès
2023-11-18 4:27 ` Maxim Cournoyer
2023-11-22 18:27 ` Ludovic Courtès
2023-11-29 16:34 ` Simon Tournier
2023-11-30 13:28 ` Maxim Cournoyer
2023-11-30 14:05 ` Guillaume Le Vaillant
2023-12-05 1:18 ` Maxim Cournoyer
2024-01-12 9:56 ` Simon Tournier
2024-01-15 4:02 ` Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86h6lmvx1i.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix@cbaines.net \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.