unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Attila Lendvai <attila@lendvai.name>
Cc: Sergey Trofimov <sarg@sarg.org.ru>, guix-devel@gnu.org
Subject: Re: Are declarative app configs worth it?
Date: Tue, 26 Dec 2023 17:49:05 +0100	[thread overview]
Message-ID: <87cyuslxgl.fsf@elephly.net> (raw)
In-Reply-To: <viSBLH0J55ZJnZEEkLOQQ26MgVrjAmKw-gT5RN2Mb9hiZB9Isxo0DpE874RNziz_AkglJs8GZoUddAPXHAizr9uHfWT7Ecv6VppX825q8tg=@lendvai.name>


Attila Lendvai <attila@lendvai.name> writes:

> if you demand that e.g. all services accepted into guix have a
> configuration entry for every possible config field, and that the
> documentation of these fields are duplicated into the guix
> codebase... then whatever is included into guix will have a 100%
> coverage. this is what is seen.

This is not what I argued for.  We also have had a couple of service
configurations that only provided options for a handful of options,
relegating all other possible options to a free text escape hatch.

There’s no point in talking percentages.

-- 
Ricardo


  reply	other threads:[~2023-12-26 17:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 13:53 Are declarative app configs worth it? Sergey Trofimov
2023-12-26 14:56 ` Ricardo Wurmus
2023-12-26 15:05   ` John Soo
2023-12-26 15:18   ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-12-26 16:50     ` Ricardo Wurmus
2023-12-27  1:34       ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-12-26 15:39   ` Attila Lendvai
2023-12-26 16:49     ` Ricardo Wurmus [this message]
2023-12-27  7:38   ` Sergey Trofimov
2023-12-28 14:28     ` Efraim Flashner
2023-12-27  4:15 ` Murad Mamedov

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=87cyuslxgl.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=sarg@sarg.org.ru \
    /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).