From: Efraim Flashner <efraim@flashner.co.il>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix gc only the rebuildable items
Date: Tue, 16 Feb 2021 22:12:54 +0200 [thread overview]
Message-ID: <YCwnRvJl71RA0HGy@3900XT> (raw)
In-Reply-To: <CAEwRq=oKk5u__C2eP4qcqxpGvMLXdum132mSb6b8iVJQC3k36w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
On Tue, Feb 16, 2021 at 08:47:31PM +0100, Vincent Legoll wrote:
> Hello,
>
> is there a way to guix gc, but only for the
> buildable items ? (I have low bandwidth /
> CPU ratio here).
>
> I.e. keep the downloadable source tarballs
> and git repo checkouts.
>
> Thanks
>
> --
> Vincent Legoll
>
To quote the manual¹
In this way, setting --gc-keep-derivations to yes causes liveness to flow from outputs to derivations, and setting --gc-keep-outputs to yes causes liveness to flow from derivations to outputs. When both are set to yes, the effect is to keep all the build prerequisites (the sources, compiler, libraries, and other build-time tools) of live objects in the store, regardless of whether these prerequisites are reachable from a GC root. This is convenient for developers since it saves rebuilds or downloads.
¹ https://guix.gnu.org/manual/devel/en/html_node/Invoking-guix_002ddaemon.html#Invoking-guix_002ddaemon
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-16 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 19:47 guix gc only the rebuildable items Vincent Legoll
2021-02-16 20:12 ` Efraim Flashner [this message]
2021-02-16 20:53 ` Vincent Legoll
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=YCwnRvJl71RA0HGy@3900XT \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=vincent.legoll@gmail.com \
/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.