From: ludo@gnu.org (Ludovic Courtès)
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 11:51:54 +0200 [thread overview]
Message-ID: <87woroieyt.fsf@gnu.org> (raw)
In-Reply-To: <87lg857nfd.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 13 Sep 2018 11:32:22 +0200")
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
>> Not yet! You could do it manually roughly by (1) listing the referrers
>> of the store item, recursively, and (2) finding the symlinks in
>> /var/guix/gcroots that point to one of these.
>
> In the example in my first message, the referrers of the .drv are either
> non-existent or the .drv itself. In this case, there should be no GC root then,
> right? Why is the item considered alive?
It’s considered live because you’re using
--gc-keep-outputs/--gc-keep-derivations, which modify the way the GC
determines whether an object is live.
If, say, “coreutils” is live, then the corresponding “coreutils.drv”
will be considered live as well when you pass --gc-keep-derivations.
Ludo’.
next prev parent reply other threads:[~2018-09-14 9:52 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 [this message]
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
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=87woroieyt.fsf@gnu.org \
--to=ludo@gnu.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).