unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <ambrevar@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: guix gc: smarter collection & guix.el manual deletion
Date: Sat, 28 Jul 2018 11:57:41 +0200	[thread overview]
Message-ID: <87fu03el7u.fsf@gmail.com> (raw)
In-Reply-To: <874lgjsokp.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]

Fantastic review!
Thank you so much for this: very clear, very thorough, it scattered all
remaining confusions!  I thumb up for a blog post! :D

While I had understood most of it, I was completely ignorant of the separation
between the .drv closure and the output closure.  It all makes much more sense now.

I think the documentation of `--gc-keep-outputs` ought to be updated.

> I don't use emacs-guix, so I can't comment on it, I'm afraid.  Maybe
> someday I'll get around to using it, and then I can say something
> useful!

I find emacs-guix tremendously useful, I highly recommend you give it a try (the
learning curve is very flat).  Any reason why you'd rather not use it?

> > While I'm at it, I'd like to note that something might be wrong with the
> > `-F` option: I never get the promised amount of free space back, only
> > about 2/3 of it.
>
> I think that's normal.  My understanding is that if you say "guix gc -F
> 3GiB", you aren't asking Guix to free 3 GiB; you're asking Guix to try
> to free enough space so that when it's done, the store will have 3 GiB
> of free space.  For example, if the store begins with 2 GiB of free
> space and there is 5 GiB of garbage, Guix will only collect 1 GiB in
> order to bring the free space up to 3 GiB.

No, I'm talking total disk usage here.  If I ask 5G back, then `df /` tells me
that root has about 3-4G free, it never has the promised amount.  Can someone
confirm this?  Might be a bug.
-- 
Pierre Neidhardt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2018-07-28  9:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  7:49 guix gc: smarter collection & guix.el manual deletion Pierre Neidhardt
2018-07-27  9:52 ` Chris Marusich
2018-07-27 19:42   ` Pierre Neidhardt
2018-07-28 10:17     ` Chris Marusich
2018-07-28 10:29       ` Pierre Neidhardt
2018-07-29 12:06         ` Chris Marusich
2018-07-29 17:33           ` Pierre Neidhardt
2018-07-29 17:48           ` Efraim Flashner
2018-07-29 18:01             ` Pierre Neidhardt
2018-07-29 23:37         ` Ludovic Courtès
2018-07-30  6:54           ` Pierre Neidhardt
2018-07-28  9:21 ` Chris Marusich
2018-07-28  9:57   ` Pierre Neidhardt [this message]

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=87fu03el7u.fsf@gmail.com \
    --to=ambrevar@gmail.com \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@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).