unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to remove old (test) builds from store?
Date: Thu, 02 Jun 2016 23:06:29 +0200	[thread overview]
Message-ID: <87eg8f2td6.fsf@gnu.org> (raw)
In-Reply-To: <57503449.9050200@crazy-compilers.com> (Hartmut Goebel's message of "Thu, 2 Jun 2016 15:27:37 +0200")

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> Am 02.06.2016 um 14:56 schrieb Thompson, David:
>> Then just run 'guix gc' and it will remove everything that isn't
>> currently included in a profile.
>
> This would remove much too much :-)

I usually run ‘guix gc -F 4G’ or similar, which removes just as much as
needed.  That works rather well for me.

> I have quite some package to work on, including those with patches
> pending for inclusion. The dependencies of these packages are not in a
> profile (yet). Now when running `guix gc`, many packages need to be
> downloaded again a few minutes later.

They “need” to be downloaded again only if you want to rebuild them,
yet without adding them to a profile or making them a GC root.  :-)

When needed, you can explicitly protect things from GC using profiles,
or using ‘guix build -r’.

Ludo’.

      parent reply	other threads:[~2016-06-02 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 10:14 How to remove old (test) builds from store? Hartmut Goebel
2016-06-02 11:10 ` 宋文武
2016-06-02 11:35   ` Hartmut Goebel
2016-06-02 12:02   ` Ludovic Courtès
2016-06-02 12:51     ` Hartmut Goebel
2016-06-02 12:56       ` Thompson, David
2016-06-02 13:27         ` Hartmut Goebel
2016-06-02 15:22           ` Leo Famulari
2016-06-02 21:06           ` Ludovic Courtès [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=87eg8f2td6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=help-guix@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.
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).