Ludovic Courtès writes:
> So you’re suggesting to systematically have a high-level interface as
> well as a lower-level interface that gives access to the raw config
> file, right?
>
> The problem is that often, the service configuration does not to just
> one config file. Often it also translate
Christopher Allan Webber skribis:
> You may remember my post to the list about how I'm interested in
> service configurations which know about each others' variables. I wrote
> about why I think this is really important to solving deployment here:
>
> http://lists.gnu.org/archive/html/guix-dev
Ludovic Courtès writes:
> "Thompson, David" skribis:
>
>> On Wed, Jan 20, 2016 at 5:13 PM, Ludovic Courtès wrote:
>>
>>> To me, the question is more about choosing between writing configuration
>>> file bindings and exposing upstream’s configuration file syntax, as was
>>> discussed when Andy po
"Thompson, David" skribis:
> On Wed, Jan 20, 2016 at 5:13 PM, Ludovic Courtès wrote:
>
>> To me, the question is more about choosing between writing configuration
>> file bindings and exposing upstream’s configuration file syntax, as was
>> discussed when Andy posted the Dovecot service. (To wh
On Wed, Jan 20, 2016 at 5:13 PM, Ludovic Courtès wrote:
> To me, the question is more about choosing between writing configuration
> file bindings and exposing upstream’s configuration file syntax, as was
> discussed when Andy posted the Dovecot service. (To which I don’t have
> a better answer
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 quas
Ricardo Wurmus writes:
> Christopher Allan Webber writes:
>
>> Though I think skribe-style string quasiquoting is not hard for a
>> schemer to learn. I picked it up almost immediately. And it's a lot
>> cleaner than the jinja2 style string templating I've grown accustomed to
>> from python web/
Christopher Allan Webber writes:
>> But I think we need some example cases first. My experiences is
>> coloured by concatenating strings for udev rules. That’s not nice, but
>> I also would not want to have to learn a new Schemey way of expressing
>> these rules — especially when I just want t
Ricardo Wurmus writes:
> Christopher Allan Webber writes:
>
>> (I've also thought that some sort of string reader similar to skribe's
>> [foo ,(bar)] string-quasiquoting may make things easier. Might even be
>> complimentary...)
>
> I like this idea. It seems unrealistic to me to have configura
Christopher Allan Webber writes:
> (I've also thought that some sort of string reader similar to skribe's
> [foo ,(bar)] string-quasiquoting may make things easier. Might even be
> complimentary...)
I like this idea. It seems unrealistic to me to have configuration file
writers for each of th
Hello all,
So I'm thinking about all the service definitions I'm going to need to
put together, and just how many different types of config files there
are out there that we're going to need to support, and etc. If we
really do produce nice scheme'y config representations for pretty much
everythi
11 matches
Mail list logo
