From: Alex Vong <alexvong1995@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Registering GC roots
Date: Fri, 16 Oct 2015 23:55:38 +0800 [thread overview]
Message-ID: <CADrxHD9i6CiGoP9nQHuG02YxrHJigc-DPCtfgqSNSq_1EawC+A@mail.gmail.com> (raw)
In-Reply-To: <87mvviizxv.fsf@gnu.org>
On 16/10/2015, Ludovic Courtès <ludo@gnu.org> wrote:
> Alex Vong <alexvong1995@gmail.com> skribis:
>
>> On 16/10/2015, Ludovic Courtès <ludo@gnu.org> wrote:
>>> Alex Vong <alexvong1995@gmail.com> skribis:
>>>
>>>> Talking about interactive CLIs, in general I am not a fan of it too,
>>>> especially after you get used to the program. That's why I am using
>>>> plain apt-get instead of aptitude which uses ncurses. However, I will
>>>> say it is sometimes useful. For example, in git clean, there is an
>>>> `-i' switch, which can help if you don't want to mess with your
>>>> .gitignore file. So perhaps making something GC roots is like putting
>>>> it in .gitignore in git, but we should still provide a way for
>>>> interacting GC-ing.
>>>
>>> Currently there are two documented ways to add GC roots from the command
>>> line: creating a profile with ‘guix package’, and using the -r option of
>>> ‘guix build.’
>>>
>>> What David suggests is to add a similar -r option to ‘guix environment’,
>>> which sounds good to me.
>>>
>> I see. So currently there is no way to make an environment GC root and
>> David is proposing using -r to achieve it. Am I right?
>
> Exactly.
>
>>> The GC process itself will not be interactive. Who would want to hit
>>> ‘y’ or ‘n’ for each one of the thousands of files considered? :-)
>>>
>> Indeed, option 3 [3. ask for every directories (like interactive
>> `rm')] looks silly. What is your opinions on a big yes/no? Perhaps it
>> is useful for beginners who may not know the "power" of GC?
>
> Like having ‘guix gc’ ask “Are you sure you want to collect garbage?”,
> with the option to bypass it with, say, ‘guix gc -f’?
>
Perhaps also showing what are being GC-ed, in the form of
PKG-NAME[VERSION] ...
or something like that since a plain question is not so useful.
My initial though is that it should be similar to running
$ apt-get autoremove --purge
Ideally, the output should not be too verbose to hurt your eyes but
verbose enough to stop from GC-ing things you don't want to GC. What
do you guys think?
> With my biased old-timer’s viewpoint ;-), I would tend to believe that
> the documentation is clear about what it means to collect garbage, and
> that the user knows what they’re doing when they press Enter.
>
> What do others think?
>
> Ludo’.
>
next prev parent reply other threads:[~2015-10-16 15:55 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
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 [this message]
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=CADrxHD9i6CiGoP9nQHuG02YxrHJigc-DPCtfgqSNSq_1EawC+A@mail.gmail.com \
--to=alexvong1995@gmail.com \
--cc=guix-devel@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.