From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 41538@debbugs.gnu.org, Marius Bakke <marius@gnu.org>
Subject: [bug#41538] [PATCH] guix scripts: Mention Guix checkouts + gcroots/auto when warning about disk space.
Date: Sat, 30 May 2020 16:05:46 +0200 [thread overview]
Message-ID: <87y2p9tt51.fsf@gnu.org> (raw)
In-Reply-To: <87d06ldcbj.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sat, 30 May 2020 11:03:28 +0200")
Hi,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Marius Bakke <marius@gnu.org> writes:
>
>> I think newbie users might not know whether it applies or not. Given
>> that 'guix gc --delete-generations' removes old generations of _all_
>> user profiles, perhaps we can just keep that instead of listing each of
>> the various ways to --delete-generations?
>
> I think this is not just about newbie users, but also a reminder of
> the full list of what you have to go through to clean up your system
> (including system profiles which take up a lot of space).
> I've used Guix for a while now and I still frequently forget to clean up
> either one of these profiles: Guix, default, non-defaults, system.
>
> I think it's fine if the list has 4 items instead of 1: if the newcomer
> does not understand everything, they'll move on. Once they do
> understand, they will be properly reminded to do it.
I checked (guix scripts gc). ‘guix gc -d’ operates on all the profiles
among the roots returned by ‘gc-roots’. This is the same as what ‘guix
package --list-profiles’ returns so it includes non-standard profiles.
You can check on your machine.
It does not include non-profile GC roots, and in particular it does not
include system generations.
Deleting a system generation involves reinstalling the bootloader (or
its config file), so it cannot be done from ‘guix gc’, at least in its
current state.
In short, ‘guix gc -d’ was introduced precisely so that one doesn’t have
to search for all the profiles, and this hint was added in the same
patch series I think. (So my earlier advice to mention ‘guix package
--list-profiles’ in the hint was actually misguided.)
The only things not handled are (1) the system, and (2) non-profile GC
roots. I think it’s OK to not mention them in the hint because these
are kinda “advanced” features.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2020-05-30 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 13:22 [bug#41538] [PATCH] guix scripts: Mention Guix checkouts + gcroots/auto when warning about disk space Pierre Neidhardt
2020-05-28 21:27 ` Ludovic Courtès
2020-05-29 9:29 ` Pierre Neidhardt
2020-05-29 11:56 ` Ludovic Courtès
2020-05-29 16:38 ` Pierre Neidhardt
2020-05-29 18:48 ` Marius Bakke
2020-05-30 9:03 ` Pierre Neidhardt
2020-05-30 14:05 ` Ludovic Courtès [this message]
2020-05-30 15:55 ` Pierre Neidhardt
2020-05-29 10:14 ` zimoun
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=87y2p9tt51.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41538@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
--cc=marius@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 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).