From: wolf <wolf@wolfsden.cz>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Csepp <raingloom@riseup.net>,
Unstable Horse <stable.master@unstable.horse>,
help-guix@gnu.org
Subject: Re: Whta is the significance of ~/.cache/guix/profiles?
Date: Thu, 29 Jun 2023 10:31:12 +0200 [thread overview]
Message-ID: <ZJ1BUPvTMIU3-stL@ws> (raw)
In-Reply-To: <CAFHYt56QaXP-G88SpfGAhwYcnZo6KfyqSGaXkyo2V9QpeRdcmg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
Hi,
On 2023-06-28 21:36:28 -0700, Felix Lechner via wrote:
> Hi Unstable Horse,
>
> > Just guessing based on a quick check of the contents of it on my
> > machine: probably serves as a cache of guix shell profiles.
>
> I also think that's what they are.
>
> Removing the links won't save much space, though. You are probably
> better off sticking to 'guix gc' unless you have a specific reason.
I do not think this is entirely accurate. The links serve as additional roots
for the garbage collector, so if your remove them, more items from the store can
be collected, possibly a lot more items. On the other hand, those links should
be automatically cleaned after some time by guix shell. So if you want to do as
thorough clean as possible, removing the links makes sense, but if you just want
to some light cleaning, you might very well leave it up to the guix shell.
>
> Kind regards
> Felix
>
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-29 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 15:07 Whta is the significance of ~/.cache/guix/profiles? Unstable Horse
2023-06-29 0:47 ` Csepp
2023-06-29 4:36 ` Felix Lechner via
2023-06-29 8:31 ` wolf [this message]
2023-06-29 17:19 ` Unstable Horse
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=ZJ1BUPvTMIU3-stL@ws \
--to=wolf@wolfsden.cz \
--cc=felix.lechner@lease-up.com \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
--cc=stable.master@unstable.horse \
/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).