From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: GC hints
Date: Wed, 19 Dec 2018 15:49:46 +0100 [thread overview]
Message-ID: <87bm5htvud.fsf@elephly.net> (raw)
In-Reply-To: <87h8f9y6cq.fsf_-_@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Actually, I was also wondering whether we should provide a configurable
> mechanism that would, by default, automatically delete old GC roots and
> maybe even run the GC automatically when needed—similar to what Git
> does.
While this would be convenient and probably an improvement I’d like to
mention that in the HPC use case this might be problematic as profiles
might be located on file shares that are not accessible by the node
running the daemon. It would be good if the GC would err on the side of
caution in those cases. (It currently removes links to unreachable
profiles.)
--
Ricardo
next prev parent reply other threads:[~2018-12-19 14:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 10:53 About /var/guix/profiles and guix pull generations Pierre Neidhardt
2018-12-09 4:35 ` Chris Marusich
2018-12-09 12:40 ` Pierre Neidhardt
2018-12-09 12:40 ` Pierre Neidhardt
2018-12-09 13:38 ` Pierre Neidhardt
2018-12-09 22:21 ` Chris Marusich
2018-12-10 8:22 ` Pierre Neidhardt
2018-12-17 9:12 ` Pierre Neidhardt
2018-12-19 2:48 ` Chris Marusich
2018-12-19 7:49 ` Pierre Neidhardt
2018-12-19 16:16 ` Chris Marusich
2018-12-19 16:28 ` Pierre Neidhardt
2018-12-19 16:31 ` Pierre Neidhardt
2018-12-19 16:49 ` Pierre Neidhardt
2018-12-25 17:51 ` swedebugia
2018-12-25 18:49 ` Pierre Neidhardt
2018-12-26 0:09 ` swedebugia
2020-05-20 8:26 ` Pierre Neidhardt
2018-12-19 13:49 ` GC hints Ludovic Courtès
2018-12-19 14:31 ` Pierre Neidhardt
2018-12-19 14:49 ` Ricardo Wurmus [this message]
2018-12-19 16:25 ` Chris Marusich
2018-12-20 12:12 ` Mark H Weaver
2018-12-20 20:03 ` Alex Kost
2018-12-21 8:30 ` Chris Marusich
2018-12-21 8:47 ` swedebugia
2018-12-23 15:58 ` Mark H Weaver
2018-12-25 12:05 ` swedebugia
2018-12-25 14:00 ` Pierre Neidhardt
2019-01-08 22:27 ` 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=87bm5htvud.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=ludo@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).