From: Matthew Brooks <matthewfbrooks@mailbox.org>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: guix gc, any way to delete only packages that aren't required to build anything?
Date: Thu, 29 Nov 2018 21:07:07 -0600 [thread overview]
Message-ID: <20181129210707.3dbf5f5a@mailbox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
Is there any recommended way to have guix gc only delete packages that aren't required to build anything?
I've made a custom bash script that loops through the output of "guix gc --list-dead" and tells guix to delete any dead packages that have no --referers, but it's really slow (it can take several hours on my laptop).
My first attempt was just telling guix to delete everything in --list-dead, but that seemed to still delete some things that were required to build other things currently on the system somewhere.
Of course, running plain "guix gc" with no arguments is much faster, but requires redownloading loads of packages whenever I next go to pull, upgrade, or install anything.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-11-30 3:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 3:07 Matthew Brooks [this message]
2018-11-30 5:15 ` guix gc, any way to delete only packages that aren't required to build anything? Ricardo Wurmus
2018-11-30 8:54 ` Pierre Neidhardt
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=20181129210707.3dbf5f5a@mailbox.org \
--to=matthewfbrooks@mailbox.org \
--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).