From: Trev <trev@fastmail.com>
To: "(" <paren@disroot.org>, GUIX Help <help-guix@gnu.org>
Subject: Re: Guix home packages and garbage collection
Date: Mon, 27 Jun 2022 15:44:26 -0700 [thread overview]
Message-ID: <97D49D17-1823-44C6-A470-E57020EAA52B@fastmail.com> (raw)
In-Reply-To: <87ilom6kp6.fsf@codinator.mail-host-address-is-not-set>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On second (or third...maybe fourth?) thought I have re-read the documentation for guix gc and it does state:
> Running guix gc with no arguments will collect
> as much garbage as it can, but that is often
> inconvenient: you may find yourself having to
> rebuild or re-download software that is “dead”
> from the GC viewpoint but that is necessary to
> build other pieces of software—e.g., the
> compiler tool chain.
https://guix.gnu.org/manual/en/html_node/Invoking-guix-gc.html
This pulls me back into wondering if I am just misusing guix gc. This behavior would feel less problematic if I accepted that I should either gc far less frequently or use something like gnu stow for environment/config instead.
On June 27, 2022 11:11:01 a.m. PDT, Trev <trev@trevdev.ca> wrote:
>"(" <paren@disroot.org> writes:
>
>> I don't experience this issue personally, and I use `guix home` for all
>> my packages. Very strange.
>>
>> -- (
>
>Thanks for helping confirm that I may have some sort of problem here. At
>the risk of admitting that I depend on non-gnu stuff in order to make my
>machine work, here's how I am set up. If I have made some sort of
>blunder, I would love to know.
>
>https://git.trevdev.ca/trevdev/guix-home-temp
>
>--
>
>Trev : 0FB7 D06B 4A2A F07E AD5B 1169 183B 6306 8AA1 D206
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-06-28 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 17:19 Guix home packages and garbage collection Trev
2022-06-27 17:39 ` (
2022-06-27 18:11 ` Trev
2022-06-27 22:44 ` Trev [this message]
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=97D49D17-1823-44C6-A470-E57020EAA52B@fastmail.com \
--to=trev@fastmail.com \
--cc=help-guix@gnu.org \
--cc=paren@disroot.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).