all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: GC hints
Date: Thu, 20 Dec 2018 07:12:16 -0500	[thread overview]
Message-ID: <874lb8xupw.fsf@netris.org> (raw)
In-Reply-To: <87h8f9y6cq.fsf_-_@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Wed, 19 Dec 2018 14:49:09 +0100")

Hi Ludovic,

Ludovic Courtès <ludo@gnu.org> writes:

> Actually, I was also wondering whether we should provide a configurable
> mechanism that would, by default, automatically delete old GC roots and
> maybe even run the GC automatically when needed—similar to what Git
> does.
>
> Thoughts?

I think it's reasonable to automatically run GC by default, but I would
strongly advise against deleting GC roots automatically by default
without the user's knowledge and consent.

It's certainly true that git performs GC automatically, but does it
automatically delete GC roots by default?  I've never seen it do this,
and I would be surprised and angry if it did.

I consider Guix GC roots to be potentially valuable user data,
regardless of age.  For example, an old GC root might be valuable
because it was used to perform an experiment that should be repeatable,
or because it is known to work reliably for a given job, and newer
versions have not yet been tested.

I, for one, expect my old profiles, system generations, and other GC
roots to be kept unless I explicitly delete them, and I suspect I'm not
alone.  If I hadn't been paying close attention to Guix development, and
later discovered that Guix had deleted my GC roots without my consent, I
would be surprised and angry.

For these reasons, I think we should not automatically delete GC roots
without the user's knowledge and consent.  User consent could be
inferred by a configuration change, or perhaps obtained interactively by
printing a warning and asking the user to give their explicit consent.

What do you think?

    Thanks,
      Mark

  parent reply	other threads:[~2018-12-20 12:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08 10:53 About /var/guix/profiles and guix pull generations Pierre Neidhardt
2018-12-09  4:35 ` Chris Marusich
2018-12-09 12:40   ` Pierre Neidhardt
2018-12-09 12:40     ` Pierre Neidhardt
2018-12-09 13:38       ` Pierre Neidhardt
2018-12-09 22:21         ` Chris Marusich
2018-12-10  8:22           ` Pierre Neidhardt
2018-12-17  9:12             ` Pierre Neidhardt
2018-12-19  2:48             ` Chris Marusich
2018-12-19  7:49               ` Pierre Neidhardt
2018-12-19 16:16                 ` Chris Marusich
2018-12-19 16:28                   ` Pierre Neidhardt
2018-12-19 16:31                     ` Pierre Neidhardt
2018-12-19 16:49                       ` Pierre Neidhardt
2018-12-25 17:51                         ` swedebugia
2018-12-25 18:49                           ` Pierre Neidhardt
2018-12-26  0:09                             ` swedebugia
2020-05-20  8:26                         ` Pierre Neidhardt
2018-12-19 13:49         ` GC hints Ludovic Courtès
2018-12-19 14:31           ` Pierre Neidhardt
2018-12-19 14:49           ` Ricardo Wurmus
2018-12-19 16:25           ` Chris Marusich
2018-12-20 12:12           ` Mark H Weaver [this message]
2018-12-20 20:03             ` Alex Kost
2018-12-21  8:30             ` Chris Marusich
2018-12-21  8:47               ` swedebugia
2018-12-23 15:58               ` Mark H Weaver
2018-12-25 12:05                 ` swedebugia
2018-12-25 14:00                   ` Pierre Neidhardt
2019-01-08 22:27                 ` Ludovic Courtès

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=874lb8xupw.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=help-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 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.