From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 56618@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#56618] [PATCH 0/2] Let 'guix gc -d' delete old Home generations
Date: Sun, 24 Jul 2022 22:04:07 -0400 [thread overview]
Message-ID: <878roi9cdk.fsf@gmail.com> (raw)
In-Reply-To: <87zgh1gwz0.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 22 Jul 2022 14:20:35 +0200")
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> Hello,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>
> [...]
>
>>> It’s an expected annoyance: to determine whether a graft needs to be
>>> applied, we first need to download/build the ungrafted variant, which is
>>> why you’re seeing this (this is worsened by the fact that many packages
>>> are candidates for grafting currently on ‘master’).
>>
>> A perhaps naive idea: could we register GC roots for the ungrafted
>> variant when grafted? To avoid having to fetch it anew following 'guix
>> gc' ?
>
> And then we need code to remove those GC roots at some point, etc. To
> me that seems like a can of worms and lack of separation of concerns.
OK.
> A related topic is GC. If personally only ever use ‘guix gc -F25G’ or
> similar; I almost never run ‘guix gc’ without arguments. Perhaps we
> should more clearly advocate that and/or have a Guix System service
> enabled by default that does something along these lines.
If I'm not mistaken, the problem with 'guix gc -F' (or guix gc) in
general, is that it doesn't start by deleting the *oldest*, i.e. the
store items the user no longer use/cares about. So you could have 'guix
gc -F25G' prune these recently fetched non-grafted variants again and
again, if you are unlucky.
Perhaps we could arrange for 'guix gc' to start deleting oldest items
first (as a default behavior)? Then the above advice would provide more
value.
Thanks,
Maxim
next prev parent reply other threads:[~2022-07-25 2:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 15:19 [bug#56618] [PATCH 0/2] Let 'guix gc -d' delete old Home generations Ludovic Courtès
2022-07-17 15:21 ` [bug#56618] [PATCH 1/2] home: Add 'home-generation-base' Ludovic Courtès
2022-07-17 15:21 ` [bug#56618] [PATCH 2/2] guix gc: '--delete-generations' now deletes old Home generations Ludovic Courtès
2022-07-18 12:51 ` [bug#56618] [PATCH 1/2] home: Add 'home-generation-base' Andrew Tropin
2022-07-19 8:01 ` Ludovic Courtès
2022-07-18 12:59 ` [bug#56618] [PATCH 0/2] Let 'guix gc -d' delete old Home generations Andrew Tropin
2022-07-19 8:28 ` Ludovic Courtès
2022-07-19 9:46 ` Andrew Tropin
2022-07-21 9:07 ` Ludovic Courtès
2022-07-21 20:10 ` Maxim Cournoyer
2022-07-22 12:20 ` Ludovic Courtès
2022-07-25 2:04 ` Maxim Cournoyer [this message]
2022-08-01 12:39 ` Ludovic Courtès
2022-07-22 22:42 ` bug#56618: " Ludovic Courtès
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=878roi9cdk.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=56618@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=ludo@gnu.org \
/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.