unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: 24965@debbugs.gnu.org
Subject: bug#24965: no openssh-service procedure
Date: Mon, 21 Nov 2016 10:04:29 +0100	[thread overview]
Message-ID: <87r365yzj6.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=RwfbscKD8pixc5brtp7L=DmfBYo4R5YH6m3_6mHE71VH2OQ@mail.gmail.com> (David Thompson's message of "Fri, 18 Nov 2016 18:38:03 -0500")

Hi David,

"Thompson, David" <dthompson2@worcester.edu> skribis:

> Despite having a bunch of procedures for making an SSH service type,
> and exporting the symbol "openssh-service" from (gnu services ssh),
> there is no openssh-service defined.  Not sure how this code made it
> in.

This is on purpose.  :-)  The manual gives this example:

          (service openssh-service-type
                   (openssh-configuration
                     (x11-forwarding? #t)
                     (permit-root-login 'without-password)))

and that’s how it should be used.  (See
<https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00095.html>.)

In recent service submissions, I’ve suggested that we stop adding
‘foo-service’ procedures and instead directly expose the
‘foo-service-type’ and ‘foo-configuration’ records.

The rationale is that the service type and config records have to be
exposed anyway if we want users to be able to customize services (with
‘modify-services’), to remove services from a list, and so on.

The downside is that it’s more typing, but I think that’s reasonable.

Thoughts?

Ludo’.

      reply	other threads:[~2016-11-21  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 23:38 bug#24965: no openssh-service procedure Thompson, David
2016-11-21  9:04 ` Ludovic Courtès [this message]

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=87r365yzj6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=24965@debbugs.gnu.org \
    --cc=dthompson2@worcester.edu \
    /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).