all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: 33124@debbugs.gnu.org
Subject: bug#33124: Cuirass: register GC roots for evaluations under /var/guix/gcroots
Date: Tue, 23 Oct 2018 11:27:30 +0200	[thread overview]
Message-ID: <877ei9ypvh.fsf@lassieur.org> (raw)

I think the goal here is to make sure that the builds that resulted from
of 1) important evaluations (releases) and 2) recent evaluations aren't
garbage collected.

--8<---------------cut here---------------start------------->8---
<sneek> snape, civodul says: i think Cuirass should register GC roots for its
	evaluations under /var/guix/gcroots
<snape> [...] How many such evaluations should be registered?  If all
	are registered, we'll run out of space won't we?  So would it be
	like the last 15 or something?
<civodul> snape: i think we'd register all of them and use (guix cache) to
	  automatically wipe old ones periodically  [09:53]
<civodul> snape: when there's a release we could manually stash important
	  evaluations away so they won't be deleted
<civodul> so i'd just create one subdir for each eval say in
	  /var/guix/profiles/USER/cuirass/evaluations  [09:54]
<civodul> and that'd contain a bunch of symlinks to both the .drv and the
	  outputs
--8<---------------cut here---------------end--------------->8---

Clément

             reply	other threads:[~2018-10-23  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  9:27 Clément Lassieur [this message]
2018-11-07 14:29 ` bug#33124: Cuirass: register GC roots for evaluations under /var/guix/gcroots Ludovic Courtès
2018-11-07 19:24   ` Clément Lassieur

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=877ei9ypvh.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=33124@debbugs.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.