unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>, Mark H Weaver <mhw@netris.org>
Cc: Guix-Help <help-guix@gnu.org>
Subject: Re: Ever-growing store with --gc-keep-outputs?
Date: Fri, 9 Nov 2018 17:47:47 +0100	[thread overview]
Message-ID: <a6b4f528-3799-35ad-8b10-93c6d33ff5cb@riseup.net> (raw)
In-Reply-To: <87efbu4iwa.fsf@ambrevar.xyz>

Hi

On 2018-11-09 11:58, Pierre Neidhardt wrote:
>> : > When I want to free up some disk space, I do the following steps:
>> : >
>> : > (1) update my user profiles and delete old generations
>> : > (2) delete older generations in /var/guix/profiles (but always
>> : >      keeping the one referenced by /run/booted-system!)
>> : > (3) reconfigure the system to remove the old system profiles from
>> : >      grub.cfg
>> : > (4) guix gc
>> : This would be nice to have in the manual I think.
>>
>> Would you like to propose a patch?
> Note that for a while Guix now suggest (1) and (4) when the store is low on
> space.
>
> I like interactive help, I think it reaches a wider audience than just the
> manual.
> Having both is also great, at the expense of risking inconsistencies if one is
> updated but not the other.
Thanks for the heads up! I totally agree. Guix is way too silent to my 
taste, comparing with e.g. pacman and git.

Generally I see the documentation in a manual as something complementing 
the program - not an excuse to keep the error messages very terse and 
refrain from gently nudging the user in the right direction.

-- 
Cheers
Swedebugia

  reply	other threads:[~2018-11-09 16:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 19:11 Ever-growing store with --gc-keep-outputs? Pierre Neidhardt
2018-09-12 10:55 ` Pierre Neidhardt
2018-09-13  9:09 ` Ludovic Courtès
2018-09-13  9:32   ` Pierre Neidhardt
2018-09-14  9:51     ` Ludovic Courtès
2018-09-14 10:57       ` Pierre Neidhardt
2018-09-14 17:46         ` Mark H Weaver
2018-09-14 18:02           ` Pierre Neidhardt
2018-09-14 21:34             ` Mark H Weaver
2018-09-14 22:10               ` Pierre Neidhardt
2018-11-09  6:53           ` swedebugia
2018-11-09  7:13             ` Mark H Weaver
2018-11-09 10:58               ` Pierre Neidhardt
2018-11-09 16:47                 ` swedebugia [this message]
2018-11-13 20:31                   ` Leo Famulari
2018-11-13 21:14                     ` swedebugia

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=a6b4f528-3799-35ad-8b10-93c6d33ff5cb@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    --cc=mhw@netris.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.
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).