From: swedebugia <swedebugia@riseup.net>
To: Chris Marusich <cmmarusich@gmail.com>, Mark H Weaver <mhw@netris.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: GC hints
Date: Fri, 21 Dec 2018 09:47:13 +0100 [thread overview]
Message-ID: <4B1F772D-4B40-43C0-BA7E-BDEBD21FEE97@pretty.Easy.privacy> (raw)
In-Reply-To: <878t10xpam.fsf@ambrevar.xyz> <87wooj1fmx.fsf@gmail.com> <87efaqna9u.fsf@ambrevar.xyz> <87d0qana9e.fsf@ambrevar.xyz> <87k1kivmzt.fsf@ambrevar.xyz> <87h8f9y6cq.fsf_-_@gnu.org> <874lb8xupw.fsf@netris.org>; <87y38j9t95.fsf@gmail.com>;
[-- Attachment #1.1: Type: text/html, Size: 1867 bytes --]
[-- Attachment #1.2: Type: text/plain, Size: 1340 bytes --]
Chris Marusich <cmmarusich@gmail.com> skrev: (21 december 2018 09:30:30 CET)
>Mark H Weaver <mhw@netris.org> writes:
>
>> 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.
>
>Just to be clear, I agree with you, Mark. Guix shouldn't delete GC
>roots automatically by default. I think we were just saying that it
>might be nice if a user could configure Guix to automatically delete GC
>roots according to some policy (e.g., retain the last 2, and delete any
>others older than 1 month). Guix would only delete the GC roots
>according to the policy that the user has set, and if no policy has
>been
>set, the default would be not to delete any of the GC roots.
>
>--
>Chris
I agree with you all 😃
This should not be the default, but be included in all the config templates with a clarifying comment.
--
Sent from my p≡p for Android.
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3825 bytes --]
next prev parent reply other threads:[~2018-12-21 8:46 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
2018-12-20 20:03 ` Alex Kost
2018-12-21 8:30 ` Chris Marusich
2018-12-21 8:47 ` swedebugia [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B1F772D-4B40-43C0-BA7E-BDEBD21FEE97@pretty.Easy.privacy \
--to=swedebugia@riseup.net \
--cc=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=mhw@netris.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).