From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: guix gc, any way to delete only packages that aren't required to build anything?
Date: Fri, 30 Nov 2018 09:54:27 +0100 [thread overview]
Message-ID: <87a7lrgd30.fsf@ambrevar.xyz> (raw)
In-Reply-To: <878t1b2lj1.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
I've been bugged by this as well (see
https://lists.gnu.org/archive/html/help-guix/2018-09/msg00028.html). There are
a few options beside Ricardo's suggestion:
- You can start the Guix daemon with --gc-keep-outputs (see "(guix) Invoking
guix-daemon" in the manual). This will never delete anything that is still
required, but this leads to an ever-growing store. If you've got limited
storage space, you might not want this.
- The Emacs mode guix.el has a nice interface for listing store items, in
particular dead items. You can sort item by size, check the number of
referrers, etc. This is much, much faster than you bash script and should
suit your needs most of the time. If you don't use Emacs, you can have still
run it in batch mode or simply re-use the Scheme code to write your own Guile
script.
Hope that helps!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-11-30 8:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 3:07 guix gc, any way to delete only packages that aren't required to build anything? Matthew Brooks
2018-11-30 5:15 ` Ricardo Wurmus
2018-11-30 8:54 ` Pierre Neidhardt [this message]
2018-11-30 20:29 ` Mark H Weaver
2018-11-30 23:14 ` Pierre Neidhardt
2018-12-01 5:13 ` Mark H Weaver
2018-12-01 13:49 ` Joshua Branson
2018-12-03 2:16 ` Mark H Weaver
2018-12-03 2:50 ` Mark H Weaver
2018-12-03 18:06 ` Joshua Branson
2018-12-10 10:27 ` Pierre Neidhardt
2018-12-11 19:40 ` George Clemmer
2018-12-12 10:38 ` Mark H Weaver
2018-12-12 23:10 ` George Clemmer
2019-01-09 19:03 ` George Clemmer
2018-12-02 14:16 ` Ludovic Courtès
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=87a7lrgd30.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).