From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 2/2] gnu: Add dovecot service Date: Wed, 16 Dec 2015 18:14:23 -0500 Message-ID: <20151216231423.GA5412@jasmine> References: <1450127388-8654-1-git-send-email-wingo@igalia.com> <1450127388-8654-2-git-send-email-wingo@igalia.com> <87fuz3co9q.fsf@gnu.org> <87wpseakfw.fsf@igalia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40119) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a9LHA-0004sK-U8 for guix-devel@gnu.org; Wed, 16 Dec 2015 18:14:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a9LH7-00041H-HF for guix-devel@gnu.org; Wed, 16 Dec 2015 18:14:28 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:52855) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a9LH6-00040y-U9 for guix-devel@gnu.org; Wed, 16 Dec 2015 18:14:25 -0500 Content-Disposition: inline In-Reply-To: <87wpseakfw.fsf@igalia.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Andy Wingo Cc: guix-devel@gnu.org 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 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