From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: guix-gc
Date: Sat, 19 Jan 2013 14:00:38 +0100 [thread overview]
Message-ID: <201301191400.38491.andreas@enge.fr> (raw)
In-Reply-To: <87hampi53a.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Am Donnerstag, 10. Januar 2013 schrieb Ludovic Courtès:
> Nix provides other options that extend this model to something closer to
> what you say, namely ‘gc-keep-outputs’ (see
> <http://hydra.nixos.org/build/3676991/download/1/nix/manual.html>.)
>
> I guess we should add a guix-daemon option for that.
If I understand the manual correctly, this is not exactly what I meant. I
thought of simply keeping all packages that are needed to build a simple
project, such as "hello". Or maybe just keeping gcc, as it takes really
very long to build. But indeed, this is less critical once binary downloads
from a build farm are possible.
Another option would be something close to debian's "apt-get autoclean":
Keep all the packages that are still available in the sense that they would
be built by calls to "guix-build", looping over the output of "guix-package
--list-available".
Andreas
[-- Attachment #2: Type: text/html, Size: 3187 bytes --]
next prev parent reply other threads:[~2013-01-19 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 23:57 guix-gc Ludovic Courtès
2013-01-10 10:04 ` guix-gc Andreas Enge
2013-01-10 12:40 ` guix-gc Ludovic Courtès
2013-01-19 13:00 ` Andreas Enge [this message]
2013-01-22 21:56 ` guix-gc Ludovic Courtès
2013-01-26 13:58 ` guix-gc Andreas Enge
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=201301191400.38491.andreas@enge.fr \
--to=andreas@enge.fr \
--cc=bug-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).