unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Cc: Ricardo Wurmus <rekado@elephly.net>, guix-devel <guix-devel@gnu.org>
Subject: Re: Building and caching old Guix derivations for a faster time machine
Date: Wed, 29 Nov 2023 17:34:26 +0100	[thread overview]
Message-ID: <87plzsr019.fsf@gmail.com> (raw)
In-Reply-To: <87h6ldiqyh.fsf@gnu.org>

Hi,

On mer., 22 nov. 2023 at 19:27, Ludovic Courtès <ludo@gnu.org> wrote:

> For long-term storage though, we could choose to keep lzip only (because
> it compresses better).  Not something we can really do with the current
> ‘guix publish’ setup though.

It looks good to me.  For me, the priority list looks like:

 1. Keep for as longer as we can all the requirements for running Guix
 itself, e.g., “guix time-machine”.  Keep all the dependencies and all
 the outputs of derivations.  At least, for all the ones the build farms
 are already building.

 2. Keep for 3-5 years all the outputs for specific Guix revision, as
 v1.0, v1.1, v1.2, v1.3, v1.4.  And some few others.

Cheers,
simon


  reply	other threads:[~2023-11-29 19:15 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
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 [this message]
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

  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=87plzsr019.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --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 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).