From: Tomas Volf <~@wolfsden.cz>
To: "Kristoffer Ström" <kristoffer@rymdkoloni.se>
Cc: Edouard Klein <edou@rdklein.fr>, help-guix@gnu.org
Subject: Re: Questions about guix-home-service-type for multi-user systems
Date: Sun, 08 Dec 2024 00:08:46 +0100 [thread overview]
Message-ID: <87msh71475.fsf@wolfsden.cz> (raw)
In-Reply-To: <87jzccef9f.fsf@rymdkoloni.se> ("Kristoffer Ström"'s message of "Fri, 06 Dec 2024 20:19:08 +0000")
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Kristoffer Ström <kristoffer@rymdkoloni.se> writes:
> Tomas Volf <~@wolfsden.cz> writes:
>
>> Edouard Klein <edou@rdklein.fr> writes:
>>
>>> The way I work around this is to use (guix-for-channels ...) in the
>>> sytem's configuration, and never guix pull. The only guix is the
>>> system's: /run/current-system/profile/bin/guix
>>
>> Out of curiosity, were you able to figure out how to cache the
>> computation, or do you live with reconfigure being a slow operation?
>
> I was just trying this out and ran into this very issue.
>
> Another problem is that a system update no longer works without an
> internet connection.
>
I managed to find a "solution" for that and described it in a blog post
here: https://wolfsden.cz/blog/post/what-goes-into-guix-shaped-hole.html
However be aware that is does have limitations and one needs to be
somewhat careful (see the update at the bottom of the article).
I just hoped someone found a better solution.
Have a nice day,
Tomas
--
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: 853 bytes --]
prev parent reply other threads:[~2024-12-07 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 20:17 Questions about guix-home-service-type for multi-user systems Kristoffer Ström
2024-12-05 11:11 ` Edouard Klein
2024-12-06 20:00 ` Tomas Volf
2024-12-06 20:19 ` Kristoffer Ström
2024-12-07 23:08 ` Tomas Volf [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87msh71475.fsf@wolfsden.cz \
--to=~@wolfsden.cz \
--cc=edou@rdklein.fr \
--cc=help-guix@gnu.org \
--cc=kristoffer@rymdkoloni.se \
/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.