all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Remove all "unreachable" objects in store
Date: Wed, 18 Jan 2017 21:58:29 +0800	[thread overview]
Message-ID: <87a8aompve.fsf@gmail.com> (raw)
In-Reply-To: <587F6AD1.2070104@crazy-compilers.com> (Hartmut Goebel's message of "Wed, 18 Jan 2017 14:17:05 +0100")

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

Hello,

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

> Hi,
>
> when packaging software, the store fills up with intermediate versions.
> I would like to get rid of these.
>
> My "production" environment typically lags behind the development head
> quite some releases. So if I run `guix gc`, this would remove quite a
> lot of packages which will then be rebuild just afterwards, when I build
> the next package. Some of these are quite big, e.g. numpy or glibc.
>
> So I'd like to garbage collect all packages which are no longer current,
> for which there is no longer a way to build them.
>
> Any ideas?

You can add '--gc-keep-outputs=yes' and '--gc-keep-derivations=yes'
flags to guix-daemon in 'guix-daemon.service' (assume you are using
systemd as init).

The relevant info can be found in
<https://www.gnu.org/software/guix/manual/guix.html#Invoking-guix_002ddaemon>.

Hope it helps, it was the question I asked on this list in the past!

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

      reply	other threads:[~2017-01-18 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 13:17 Remove all "unreachable" objects in store Hartmut Goebel
2017-01-18 13:58 ` Alex Vong [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a8aompve.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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.