From: "Ludovic Courtès" <ludo@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 38469-done@debbugs.gnu.org
Subject: bug#38469: guix gc should keep around recent intermediate build
Date: Tue, 10 Dec 2019 17:39:07 +0100 [thread overview]
Message-ID: <87pngwnnis.fsf@gnu.org> (raw)
In-Reply-To: <A0E5ED6B-5E4F-4AF3-A745-7FA2E7336AA5@vllmrt.net> (Robert Vollmert's message of "Tue, 3 Dec 2019 15:29:00 +0100")
Hi,
Robert Vollmert <rob@vllmrt.net> skribis:
>> Have you tried passing the options '--gc-keep-derivations=yes’ and
>> '--gc-keep-outputs=yes' to guix-daemon?
>
> I had not. I added that right now, and first tests seem to indicate
> that this helps. Thanks!
Yes, I think these options are exactly what you want.
> Would it be a bad idea to make this the default?
I think the current defaults are more appropriate; after all, they
really allow “garbage” to be collected.
> Alternatively, how about some kind of developer config fragment that
> would modify a system configuration with settings that are a good
> idea for Guix development, if not general use? That might also include
> things like setting the $%!^@!*^% guile backtrace columns variable
> for guix-daemon.
I think what you’d want is to set COLUMNS within derivation, not “for
the daemon”.
So I don’t know, I’m sympathetic to the idea of developer settings in
Guix System, but I’m not sure what it could bring beyond these two
options.
In the meantime, I propose to close this bug and to discuss this
potential new feature separately.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-12-10 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 10:48 bug#38469: guix gc should keep around recent intermediate build ingredients by default Robert Vollmert
2019-12-03 12:59 ` Guillaume Le Vaillant
2019-12-03 14:29 ` bug#38469: guix gc should keep around recent intermediate build Robert Vollmert
2019-12-10 16:39 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pngwnnis.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38469-done@debbugs.gnu.org \
--cc=rob@vllmrt.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.