unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add dovecot service
Date: Wed, 16 Dec 2015 18:14:23 -0500	[thread overview]
Message-ID: <20151216231423.GA5412@jasmine> (raw)
In-Reply-To: <87wpseakfw.fsf@igalia.com>

On Wed, Dec 16, 2015 at 08:04:19AM +0000, Andy Wingo wrote:
> On Tue 15 Dec 2015 22:58, ludo@gnu.org (Ludovic Courtès) writes:
> > Andy Wingo <wingo@igalia.com> skribis:
> >
> >> * gnu/services/mail.scm: New file.
> >
> > Regarding the Schemefied configuration, do you think Dovecot’s
> > configuration model is stable enough that this won’t have to change
> > much?  Is a “cheat mode” (where one can pass raw strings to paste into
> > the configuration file) needed?
> 
> Finally, I'm not adverse to a .conf file escape hatch.  It's especially
> convincing in a context where other services do the same -- we should
> have a greater degree of uniformity across services.  However if other
> services implemented a 100%-solution Scheme configuration interface, I
> wonder if we would still want the .conf file interface.  Dunno!

For 3rd party software, I think we should make it possible for users to
use upstream's configuration language, preferably as a text block inside
of the service configuration block.

Otherwise, it will be difficult for users to migrate to GuixSD, since
their existing configuration files and their knowledge won't apply.
Plus, it will make it more difficult for our users to get support for
the 3rd party software if it is configured in an unfamiliar way.

I'm wary of this approach based on my experiences with systemd on NixOS,
where only some features of systemd are exposed by the Nix wrapper. [0]
Now _that_ is a frustrating 80% solution.

On the other hand, being able to reuse my existing nginx.conf within
configuration.nix was very convenient.

[0]
https://github.com/NixOS/nixpkgs/issues/1689
https://github.com/NixOS/nixpkgs/issues/3702

  reply	other threads:[~2015-12-16 23:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 21:09 [PATCH 1/2] gnu: dovecot: Add linux-pam to inputs Andy Wingo
2015-12-14 21:09 ` [PATCH 2/2] gnu: Add dovecot service Andy Wingo
2015-12-15 22:58   ` Ludovic Courtès
2015-12-16  8:04     ` Andy Wingo
2015-12-16 23:14       ` Leo Famulari [this message]
2015-12-17  9:22         ` Andy Wingo
2015-12-17 14:23           ` Ludovic Courtès
2015-12-17 15:38         ` Christopher Allan Webber
2015-12-18  0:59           ` Leo Famulari
2015-12-18  9:26   ` Andy Wingo
2015-12-15 22:45 ` [PATCH 1/2] gnu: dovecot: Add linux-pam to inputs Ludovic Courtès

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=20151216231423.GA5412@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.com \
    /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).