From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Proposal: auto-instantiate services with a default value
Date: Tue, 09 Jan 2018 21:42:28 +0100 [thread overview]
Message-ID: <87wp0qsr0r.fsf@gnu.org> (raw)
In-Reply-To: <87r2qzqhc2.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 09 Jan 2018 14:42:21 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>>> Also, that means that the instantiated mcron-service would automatically get a rottlog entry even though the mcron-service-types's default job list is empty, right ?
>>
>> Correct.
>>
>>> In that case it would be nice to be able to (optionally) override this mcron-service by a custom mcron-service in /etc/config.scm but retain the modified configuration with the implicit job in it. Is that possible?
>>
>> Sure, the current way to do things (which is to explicitly list rottlog
>> *and* mcron) would remain valid, and you could pass your own mcron
>> config this way.
>
> If a user already had an mcron service with a custom configuration,
> it would still be extended as needed by adding the rottlog-service — or
> am I mistaken?
Yes. Basically an existing currently-working configuration will still
work exactly the same.
The novelty is that one would now be able to omit services that are
indirectly needed.
> I think auto-instantiation is great when it all shows up with “guix
> system extension-graph” and users can thus figure out why certain
> services were instantiated unexpectedly.
Yes. Speaking of which, it’d be great to have an interactive view of
service folding (d3.js?)…
Ludo’.
next prev parent reply other threads:[~2018-01-09 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 9:05 Proposal: auto-instantiate services with a default value Ludovic Courtès
2018-01-09 10:16 ` ng0
2018-01-09 10:59 ` Danny Milosavljevic
2018-01-09 12:25 ` Ludovic Courtès
2018-01-09 13:42 ` Ricardo Wurmus
2018-01-09 20:42 ` Ludovic Courtès [this message]
2018-01-10 6:56 ` Chris Marusich
2018-01-20 23:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wp0qsr0r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.