From: antlers <antlers@illucid.net>
To: edk@beaver-labs.com
Cc: guix-devel@gnu.org
Subject: Re: A friendlier API for operating-system declarations
Date: Mon, 19 Feb 2024 14:25:51 -0800 [thread overview]
Message-ID: <1a7168a5-5207-4dfa-ac12-b3fed841580b@app.fastmail.com> (raw)
Hi!
Just wanted to say that I really admire your take on end-user service configuration in the Beaver Labs channel.
I gravitated towards composing functions over `operating-systems` myself, though my config is probably only ""notable"" for the moderately-cursed `modify-record` macro that I use to derive/configure/wrap the services[1]:
```
(define (os-with-yubi parent users*)
(modify-record parent
(groups -> (cons (user-group (name "plugdev")) <>))
(users -> (map (lambda (user)
(if (member (user-account-name user)
users*)
(modify-record user
(supplementary-groups -> (cons "plugdev" <>)))
user))
<>))
(services => (append <> (list
(service pcscd-service-type)
(simple-service 'u2f-udev-rules udev-service-type
(list (specification->package "libu2f-host")))
(simple-service 'yubi-udev-rules udev-service-type
(list (specification->package "yubikey-personalization"))))))))
```
It's like if `modify-services` was generalized over any kind of record, but instead of using pre-defined verbs like `remove`, the `body` component of each `(field-name -> body)` clause is wrapped in an implicit SRFI-26 `cut`-like[2] form to create an anonymous function that's applied to the field's value. It's a super leaky abstraction because I use a different symbol for `->` depending on whether that record-field is a plain value, a thunk, or a `delay`-ed form (and it could be implemented more efficiently), but it greatly reduces the length and indentation level of repeatedly nested, inherited record variations.
```
((compose os-with-yubi
[...])
[operative-system])
```
I only wrote a handful of top-level `operating-system transformation` functions, and IIRC I only composed them at that top level; I think the way that you've broken them up into smaller forms and composed them out of each other though deeper, standard-functional composition gives you that same additive benefit over would-be nested forms, with each definition roughly matching up to one my "anonymous" invocations.
What I still dwell on is whether there's a way to further minimize the code-volume of including additional functionality (as was pondered in a prior response, and as `modify-record` does in obsoleting `modify-services`'s verbs), and how best to avoid order-dependencies and expose inherit inter-service-configuration dependencies and conflicts. Tropin's RDE uses an emacs or systemd-esque `provides`/`requires` system which is satisfying, but introduces implicit standardization on the symbols associated with software roles and builds a significant graph of them, which I feel adds to the "bulk" of the (still very elegant) solution and embraces the need to wrap every service and transformation into their cohesive system-- that's part of what's kept me on plain Guix with my bandaid-solutions (in the spirit of learning the standard approach before exploring larger systems built on top of it).
Anyway, I like your take, just fount it today and got to thinking-- thanks for putting it out there~
1: From: https://github.com/AutumnalAntlers/old-guix-config/blob/main/modules/antlers/systems/transformations/yubi.scm
2: Like `cut`, but deeper: see the `<>` symbol nested deep within in the `users` clause of the Yubi example.
next reply other threads:[~2024-02-24 21:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 22:25 antlers [this message]
[not found] ` <87plwrj3w9.fsf@rdklein.fr>
2024-02-20 3:42 ` A friendlier API for operating-system declarations antlers
2024-02-25 9:26 ` Liliana Marie Prikler
2024-02-25 18:49 ` antlers
2024-02-25 20:47 ` antlers
2024-02-25 20:50 ` Liliana Marie Prikler
2024-02-25 21:27 ` antlers
2024-02-26 19:58 ` Liliana Marie Prikler
2024-03-01 16:44 ` Hartmut Goebel
-- strict thread matches above, loose matches on Subject: below --
2023-05-19 3:31 antlers
2023-03-23 8:06 Edouard Klein
2023-03-23 18:48 ` Josselin Poiret
2023-03-23 20:23 ` Edouard Klein
2023-03-23 21:05 ` Liliana Marie Prikler
2023-04-13 9:42 ` Ludovic Courtès
2023-05-18 14:37 ` Edouard Klein
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=1a7168a5-5207-4dfa-ac12-b3fed841580b@app.fastmail.com \
--to=antlers@illucid.net \
--cc=edk@beaver-labs.com \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).