From: Edouard Klein <edou@rdklein.fr>
To: help-guix@gnu.org
Subject: Re: Modular home configuration
Date: Sat, 09 Nov 2024 20:30:59 +0100 [thread overview]
Message-ID: <D48AF3A7-56ED-43B1-907C-E32597F7BAA1@rdklein.fr> (raw)
In-Reply-To: <87y11s1ekj.fsf@meson>
The magic is here <https://gitlab.com/edouardklein/guix/-/blob/beaverlabs/beaver/functional-home-services.scm?ref_type=heads>
Le 9 novembre 2024 18:35:10 GMT+01:00, Ian Eure <ian@retrospec.tv> a écrit :
>Hi folks,
>
>I’m trying to make my home configuration more modular, so I can better support system variances. For example, I have a laptop I use interactively, and a headless machine that runs Cuirass. It’s advantageous to share certain aspects of the home configuration between the two machines (shell prompt/environment, GPG agent, etc), but not others (anything X11/graphical stuff shouldn’t be on the build machine). One approach to this is to define packages and services and reference them in the home configuration. What I dislike about this is that many things require both packages and services, and I’d prefer to have a way to completely encapsulate that -- for example, the mpd-mpc package to control my music server, plus a home-environment-variables-service-type to set MPD_HOST.
>
>I attempted to solve this by writing a procedure:
>
> (define (+mpd-client home-config)
> (home-environment
> (inherit home-config)
> (packages (cons mpd-mpc (home-environment-packages home-config)))
> (services
> (cons
> (simple-service
> 'mpd-environment-service
> home-environment-variables-service-type
> '(("MPD_HOST" . "audio.box")))
> (home-environment-services home-config)))))
>
>Which I can then wrap around a home-environment to add the mpd-mpc package and environment variable it needs to work:
>
> (+mpc-client (home-environment ...))
>
>Surprisingly, this doesn’t work -- it complains that there’s more than one "home" service type. I’m not sure why that is, and I haven’t been able to see anything obviously wrong in the REPL -- though I haven’t been able to get my actual home configuration up in the Emacs-Guix REPL, due to #67290.
>
>Does anyone have a suggestion for a workaround for this issue, explanation of how two home services are ending up in the config, or a better approach for building modular home configs?
>
>Thanks,
>
> — Ian
>
prev parent reply other threads:[~2024-11-09 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 17:35 Modular home configuration Ian Eure
2024-11-09 19:09 ` Tomas Volf
2024-11-09 19:30 ` Edouard Klein
2024-11-09 19:30 ` Edouard Klein [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=D48AF3A7-56ED-43B1-907C-E32597F7BAA1@rdklein.fr \
--to=edou@rdklein.fr \
--cc=help-guix@gnu.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).