From: Mark H Weaver <mhw@netris.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-Help <help-guix@gnu.org>
Subject: Re: Ever-growing store with --gc-keep-outputs?
Date: Fri, 14 Sep 2018 17:34:34 -0400 [thread overview]
Message-ID: <87ftybhifp.fsf@netris.org> (raw)
In-Reply-To: <87tvms555s.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Fri, 14 Sep 2018 20:02:07 +0200")
Pierre Neidhardt <mail@ambrevar.xyz> writes:
>> it works well in my preferred mode of operation where I
>> build everything locally and never use substitutes.
>
> Do substitutes change the way GC behaves? I use substitutes.
No. However, if you build everything locally, it becomes more important
to avoid deleting store items that will be needed to build your next
system update, and so the --gc-keep-* flags become important.
>> (1) update my user profiles and delete old generations
>> (2) delete older generations in /var/guix/profiles (but always
>> keeping the one referenced by /run/booted-system!)
>
> You mean system generations? I did that.
Right.
>> (3) reconfigure the system to remove the old system profiles from
>> grub.cfg
>> (4) guix gc
>
> I did all this. Then ghc-pandoc and all the ghc dependencies did not go.
What is the output of "guix gc --referrers /gnu/store/xxxxx.drv" when
applied to the .drv file for ghc-pandoc?
Mark
next prev parent reply other threads:[~2018-09-14 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 19:11 Ever-growing store with --gc-keep-outputs? Pierre Neidhardt
2018-09-12 10:55 ` Pierre Neidhardt
2018-09-13 9:09 ` Ludovic Courtès
2018-09-13 9:32 ` Pierre Neidhardt
2018-09-14 9:51 ` Ludovic Courtès
2018-09-14 10:57 ` Pierre Neidhardt
2018-09-14 17:46 ` Mark H Weaver
2018-09-14 18:02 ` Pierre Neidhardt
2018-09-14 21:34 ` Mark H Weaver [this message]
2018-09-14 22:10 ` Pierre Neidhardt
2018-11-09 6:53 ` swedebugia
2018-11-09 7:13 ` Mark H Weaver
2018-11-09 10:58 ` Pierre Neidhardt
2018-11-09 16:47 ` swedebugia
2018-11-13 20:31 ` Leo Famulari
2018-11-13 21:14 ` swedebugia
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=87ftybhifp.fsf@netris.org \
--to=mhw@netris.org \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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).