all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Mathieu Lirzin <mthl@openmailbox.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Plan for 0.9.0
Date: Thu, 15 Oct 2015 09:10:09 -0400	[thread overview]
Message-ID: <CAJ=RwfbY=JoQGo_sTBV=sOYqDPA5R+x1MDq8GTptZKia-_tZBw@mail.gmail.com> (raw)
In-Reply-To: <87vba8gurr.fsf@openmailbox.org>

On Thu, Oct 15, 2015 at 8:51 AM, Mathieu Lirzin <mthl@openmailbox.org> wrote:
> "Thompson, David" <dthompson2@worcester.edu> writes:
>
>> On Thu, Oct 15, 2015 at 8:28 AM, Mathieu Lirzin <mthl@openmailbox.org> wrote:
> [...]
>>> I think the enthusiasm for changing ‘guix gc’ was induced by somekind of
>>> shared experience of typing it loosely and ending up having to download
>>> a lot of substitutes again.  So maybe we can keep ‘guix gc’ as it is but
>>> make it interactive by listing what is going to be deleted and ask for
>>> confirmation with a [Y/n] prompt.  This solution will also require
>>> somekind of a ‘--force’ option for scripting purposes.
>>>
>>> Does it sound better?
>>
>> In general, I do not like interactive CLIs.  I'm fine with 'guix gc'
>> working as-is.  The re-downloading lots of substitutes issue is not an
>> issue about the CLI, but rather about not making store items that you
>> want to hang around GC roots.
>
> You mean a problem between the keyboard and the chair, or a problem with
> the GC being too greedy?

The GC is not too greedy.  It's doing exactly what it should.  The
issue is that we need more tools to let people protect things from the
GC that they want protected.  One example that is that 'guix
environment' will eventually generate profiles that are registered as
GC roots, which will protect development environments from the GC.

- Dave

  reply	other threads:[~2015-10-15 13:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 21:19 Plan for 0.9.0 Ludovic Courtès
2015-10-13 13:15 ` Daniel Pimentel
2015-10-13 14:37   ` Ludovic Courtès
2015-10-13 15:01   ` Alex Vong
2015-10-13 15:27     ` Ricardo Wurmus
2015-10-13 18:26       ` Mathieu Lirzin
2015-10-13 18:30         ` Taylan Ulrich Bayırlı/Kammer
2015-10-14 19:58     ` Ludovic Courtès
2015-10-14 20:06       ` Mathieu Lirzin
2015-10-14 21:44         ` Ludovic Courtès
2015-10-14 22:02           ` Eric Bavier
2015-10-15 12:28             ` Mathieu Lirzin
2015-10-15 12:33               ` Thompson, David
2015-10-15 12:51                 ` Mathieu Lirzin
2015-10-15 13:10                   ` Thompson, David [this message]
2015-10-15 13:15                     ` Daniel Pimentel
2015-10-15 14:11                       ` Christopher Allan Webber
2015-10-15 14:43                         ` Ludovic Courtès
2015-10-15 13:40                     ` Mathieu Lirzin
2015-10-15 15:31                 ` Taylan Ulrich Bayırlı/Kammer
2015-10-15 19:27                   ` Ludovic Courtès
2015-10-16  4:14                 ` Alex Vong
2015-10-16  7:44                   ` Mathieu Lirzin
2015-10-16 11:09                     ` Alex Vong
2015-10-16  8:10                   ` Registering GC roots Ludovic Courtès
2015-10-16 12:56                     ` Alex Vong
2015-10-16 15:41                       ` Ludovic Courtès
2015-10-16 15:55                         ` Alex Vong
2015-10-16 17:21                           ` Andreas Enge
2015-10-16 16:28                         ` Mathieu Lirzin
2015-10-15 14:41               ` Plan for 0.9.0 Ludovic Courtès
2015-10-15 15:07                 ` Mathieu Lirzin
2015-11-02  9:45 ` 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='CAJ=RwfbY=JoQGo_sTBV=sOYqDPA5R+x1MDq8GTptZKia-_tZBw@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    --cc=mthl@openmailbox.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.