From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: guix-gc
Date: Tue, 22 Jan 2013 22:56:57 +0100 [thread overview]
Message-ID: <87r4lc51au.fsf@gnu.org> (raw)
In-Reply-To: <201301191400.38491.andreas@enge.fr> (Andreas Enge's message of "Sat, 19 Jan 2013 14:00:38 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> 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.
I’ve actually installed or registered roots for such “precious”
packages, which prevents them from being GC’d.
> 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".
For packages that use ‘gnu-build-system’, the prerequisites are a
superset of (@ (gnu packages base) final-inputs), which includes GCC,
Coreutils, libc, etc. So you would want to keep those, I guess, right?
OTOH, imagine a hypothetical ‘python-build-system’, whose only implicit
inputs are Python and perhaps Coreutils. Someone who only installs
Python packages only cares about keeping Python and Coreutils around.
And then, the GC. The GC only sees derivations, and derivation outputs.
It doesn’t have the slightest idea of which outputs are valuable to the
user, and which aren’t.
So the normal way to address this problem is to tell the GC what’s
important: by installing packages, or by running ‘guix-build --root’.
The Nix daemon options I mentioned above can be used to do something
more: keeping the source tarballs of derivations whose outputs are still
present.
But as you note, all this will be much less of a concern when we can
download pre-built binaries. Something to get in for 0.2, I guess. :-)
WDYT?
Ludo’.
next prev parent reply other threads:[~2013-01-22 21:57 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 ` guix-gc Andreas Enge
2013-01-22 21:56 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r4lc51au.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=bug-guix@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 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.