unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: wishlist: “repack” generations history of profile
Date: Mon, 23 May 2022 17:42:07 +0200	[thread overview]
Message-ID: <87tu9g2r3k.fsf@gnu.org> (raw)
In-Reply-To: <86wnegb9it.fsf@gmail.com> (zimoun's message of "Fri, 20 May 2022 15:47:54 +0200")

Hello!

zimoun <zimon.toutoune@gmail.com> skribis:

> The question is what to do when we delete?
>
> I am proposing to delete the content, i.e., all but keep the meta, i.e.,
> the file manifest.  We could have an option soft (keep meta) and hard
> (remove all, meta included, as today) for guix gc.

Exactly!  ‘guix pull’ profiles are entirely reproducible: we can rebuild
them from the output of ‘guix describe’.

So ‘guix gc’ (or something) could automatically remove old generation
symlinks and instead store the output of ‘guix describe’.  That way,
‘--list-generations’ or ‘--switch-generations’ could transparently
display the info or rebuild the generation.

System and Home generations are usually, but not necessarily,
reproducible: usually the channel info + config file are enough to
rebuild them, but in theory the config file might refer to resources not
known to Guix (e.g., SSH key files, modules, whatever).  That said, we
could arrange so that ‘guix gc -d’ keeps the metadata around.

For regular profiles, we might do the same, but no guarantee we can
rebuild them, unless all the packages come from the same channels (which
is the case if the profile was built with ‘guix package -m’).

Ludo’.


  parent reply	other threads:[~2022-05-23 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 13:47 wishlist: “repack” generations history of profile zimoun
2022-05-21 11:30 ` Liliana Marie Prikler
2022-05-23 16:20   ` zimoun
2022-05-23 15:42 ` Ludovic Courtès [this message]
2022-05-23 16:58   ` zimoun
2022-05-30 15:40     ` Ludovic Courtès
2022-05-30 17:18       ` zimoun
2022-06-04  7:39         ` Giovanni Biscuolo
2022-06-05  9:45           ` zimoun
2022-06-05 11:16             ` Giovanni Biscuolo

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