all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, Dika Setya Prayogi <dikasetyaprayogi@gmail.com>
Subject: Re: a bit curiousity
Date: Tue, 22 Dec 2015 17:54:28 +0100	[thread overview]
Message-ID: <87mvt2bf0b.fsf@gnu.org> (raw)
In-Reply-To: <87y4cm7bgy.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 22 Dec 2015 16:24:29 +0100")

Ricardo Wurmus <rekado@elephly.net> skribis:

> Dika Setya Prayogi <dikasetyaprayogi@gmail.com> writes:

[...]

>> 2.set auto garbage collect for package old than one month
>
> Garbage collection is not about age but about references.  If a package
> is referenced in a profile (even if it’s not the latest generation of
> the profile) it won’t be collected.  This is a feature.
>
> To achieve garbage collection of old packages you would have to remove
> all old profile generations (so that older packages are no longer
> referenced), and also make sure that no “old” packages are referenced in
> the current profile generation.  This essentially requires a forced
> upgrade with deletion of older profile generations, which seems quite
> unwise.  You’d throw away some of the best features of Guix, in my
> opinion.

One could have a periodic job that runs:

  guix package --delete-generations=1m && guix gc

This removes generations older than 1 month and then runs the GC.

Depending on your use case, this may or may not be a good idea.  I
personally prefer to remove generations once I know I’m very unlikely to
ever need to roll back to them.

Ludo’.

  parent reply	other threads:[~2015-12-22 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 10:48 a bit curiousity Dika Setya Prayogi
2015-12-22 15:24 ` Ricardo Wurmus
2015-12-22 15:44   ` Andy Wingo
2015-12-22 16:54   ` Ludovic Courtès [this message]
2015-12-23  7:56     ` Dika Setya Prayogi
2015-12-23  7:59     ` Dika Setya Prayogi

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=87mvt2bf0b.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dikasetyaprayogi@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.