unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 34955@debbugs.gnu.org
Subject: bug#34955: Manual: Service extensions not clear
Date: Sat, 23 Mar 2019 16:46:21 +0100	[thread overview]
Message-ID: <20190323154621.u5kjvvgcci7ikrbt@pelzflorian.localdomain> (raw)

The Guix manual (section Defining services) says about service
extensions:

[The example guix-service-type definition] defines three things:

  1. […]

  2. A list of “service extensions”, where each extension designates the
     target service type and a procedure that, given the parameters of
     the service, returns a list of objects to extend the service of
     that type.

     Every service type has at least one service extension.  The only
     exception is the “boot service type”, which is the ultimate
     service.

This is confusing to me because previously it was explained that
services extend services but now it says types extend types which does
not fit the previous explanation.

Later it says:

   There can be only one instance of an extensible service type such as
UDEV-SERVICE-TYPE.  If there were more, the ‘service-extension’
specifications would be ambiguous.

I believe before the example for the definition of service types,
service extensions should be explained.

E.g.

A service type definition specifies which services can be extended by
an instance of the service type.  For each service extension, exactly
one service of the target service type of the extension must appear
in the services field of the operating-system declaration.

Regards,
Florian

                 reply	other threads:[~2019-03-23 15:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190323154621.u5kjvvgcci7ikrbt@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=34955@debbugs.gnu.org \
    /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).