From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andrew Tropin <andrew@trop.in>
Cc: guix-devel@gnu.org, Xinglu Chen <public@yoctocell.xyz>,
guix-maintainers@gnu.org
Subject: Re: Return back original implementation for text-config serialization
Date: Thu, 27 Jan 2022 00:04:13 -0500 [thread overview]
Message-ID: <87fsp922ia.fsf@gmail.com> (raw)
In-Reply-To: <87h79qx5db.fsf@trop.in> (Andrew Tropin's message of "Wed, 26 Jan 2022 11:34:24 +0300")
Hi Andrew,
Andrew Tropin <andrew@trop.in> writes:
[...]
> Ludovic mentioned someday that nginx-configuration is problematic, but I
> highlighted the generic problems, which are applicable for many other
> guix service configurations.
>
> I discussed some other pros and cons of record-based configurations in
> https://issues.guix.gnu.org/52698
>
> and I see the benifits of the records, but I'm not sure if they
> outweight the weaknesses.
>
> It maybe sound unrelated to this thread, but it's actually very ontopic,
> because it lead to the design and implementation of home services
> configuration approach in general and slurp-file-gexp and text-config in
> particular.
Pardon my ignorance about Guix Home, but couldn't we have configuration
as records by default, and the lower level, config stitching primitives
still available to hand craft strings that could be used as the value of
an 'extra-config' field, for example?
It seems to me the use of records for configurations in Guix Home would
be the natural choice, as Guix System users are already familiar with
them and it leans to better discoverability/documentation.
Thanks,
Maxim
next prev parent reply other threads:[~2022-01-27 5:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 9:12 Return back original implementation for text-config serialization Andrew Tropin
2022-01-09 11:19 ` Liliana Marie Prikler
2022-01-09 17:48 ` Andrew Tropin
2022-01-09 19:44 ` Liliana Marie Prikler
2022-01-10 9:49 ` Andrew Tropin
2022-01-10 20:12 ` Liliana Marie Prikler
2022-01-12 15:05 ` Andrew Tropin
2022-01-09 12:17 ` Maxime Devos
2022-01-09 12:19 ` Maxime Devos
2022-01-09 17:59 ` Andrew Tropin
2022-01-09 19:00 ` Maxime Devos
2022-01-18 14:26 ` Ludovic Courtès
2022-01-20 13:20 ` Andrew Tropin
2022-01-21 9:30 ` Maxime Devos
2022-01-26 8:34 ` Andrew Tropin
2022-01-27 5:04 ` Maxim Cournoyer [this message]
2022-01-28 15:48 ` Andrew Tropin
2022-02-05 11:09 ` Ludovic Courtès
2022-02-13 14:14 ` Andrew Tropin
2022-01-26 8:36 ` Andrew Tropin
2022-02-05 11:34 ` Maxime Devos
2022-02-13 14:09 ` Andrew Tropin
2022-01-24 15:37 ` Ludovic Courtès
2022-01-26 9:11 ` Andrew Tropin
2022-01-26 9:21 ` Andrew Tropin
2022-02-05 14:43 ` Xinglu Chen
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=87fsp922ia.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=public@yoctocell.xyz \
/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.