no openssh-service procedure

  • Done
  • quality assurance status badge
Details
2 participants
  • Thompson, David
  • Ludovic Courtès
Owner
unassigned
Submitted by
Thompson, David
Severity
normal
T
T
Thompson, David wrote on 19 Nov 2016 00:38
(address . bug-guix@gnu.org)
CAJ=RwfbscKD8pixc5brtp7L=DmfBYo4R5YH6m3_6mHE71VH2OQ@mail.gmail.com
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.

- Dave
L
L
Ludovic Courtès wrote on 21 Nov 2016 10:04
(name . Thompson, David)(address . dthompson2@worcester.edu)(address . 24965@debbugs.gnu.org)
87r365yzj6.fsf@gnu.org
Hi David,

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

Toggle quote (5 lines)
> 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

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’.
L
L
Ludovic Courtès wrote on 11 Jan 2017 23:10
control message for bug #24965
(address . control@debbugs.gnu.org)
87y3yhuu2f.fsf@gnu.org
tags 24965 notabug
close 24965
?
Your comment

This issue is archived.

To comment on this conversation send an email to 24965@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 24965
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch