From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Composing service definitions (and maybe fmt) Date: Wed, 20 Jan 2016 23:13:11 +0100 Message-ID: <87si1rx5l4.fsf@gnu.org> References: <87oacloy61.fsf@dustycloud.org> <87fuxt5zh9.fsf@dustycloud.org> <87vb6ogmqw.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33037) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aM10A-000168-Mg for guix-devel@gnu.org; Wed, 20 Jan 2016 17:13:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aM107-0000IG-B3 for guix-devel@gnu.org; Wed, 20 Jan 2016 17:13:18 -0500 In-Reply-To: <87vb6ogmqw.fsf@dustycloud.org> (Christopher Allan Webber's message of "Wed, 20 Jan 2016 09:49:57 -0800") 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: Christopher Allan Webber Cc: guix-devel@gnu.org Christopher Allan Webber skribis: > Ludo, you've actually done quite a bit of skribe-style-stuff work! :) > Do you think this is a good idea? And what would be the right approach? > Depending on guile-reader may be a bit heavy for Guix (?), though maybe > writing a reader macro to do string quasiquoting will not be hard anyway. I think we don=E2=80=99t want to depend on guile-reader, and I=E2=80=99m ra= ther against reader macros, except on rare occasions like #' and #~, because they could interfere with other extensions that people use. The Skribe syntax is just literal-text-by-default, where [foo bar ,baz] is equivalent to: (list "foo bar " baz) It=E2=80=99s convenient when writing document, but I=E2=80=99m not sure it = is so helpful for config files. For instance, =E2=80=98text-file*=E2=80=99 and =E2=80=98= mixed-text-file=E2=80=99 get close to that, but without the reader macro. See xorg.scm for example. To me, the question is more about choosing between writing configuration file bindings and exposing upstream=E2=80=99s configuration file syntax, as= was discussed when Andy posted the Dovecot service. (To which I don=E2=80=99t = have a better answer than: let=E2=80=99s see on a case-by-case basis.) WDYT? But yeah, maybe we need a concrete example to illustrate the various options. :-) Thanks, Ludo=E2=80=99.