unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: Guix Devel <guix-devel@gnu.org>, Andrew Tropin <andrew@trop.in>
Subject: Re: SSH service for Guix Home
Date: Mon, 20 Dec 2021 23:31:10 +0100	[thread overview]
Message-ID: <87ilvidi35.fsf@gnu.org> (raw)
In-Reply-To: <877dc3jor3.fsf@disroot.org> (Xinglu Chen's message of "Fri, 17 Dec 2021 15:21:36 +0100")

Hi!

Xinglu Chen <public@yoctocell.xyz> skribis:

> On Wed, Dec 15 2021, Ludovic Courtès wrote:
>
>> Hi Andrew,
>>
>> One service I miss for Guix Home is ‘home-ssh-service-type’, which is in
>> the “original” Guix Home.
>>
>> Could you contribute a patch adding it?  (I could do it on your behalf,
>> but it sounds more logical to let you handle it.)
>
> Being the original author, I will hopefully try to work on it soon.  :-)

Neat.  :-)

[...]

>> Last, it’d be great to see the three of you (and more people!) back in
>> action regarding Guix Home.  I understand that life sometimes gets in
>> the way, but it seems that there’s been some confusion as to how to go
>> forward—e.g., <https://issues.guix.gnu.org/51359#2>—which may partly
>> explain why things stalled.  If there are patches waiting for review,
>> also don’t hesitate to ping!
>
> Yeah, apologies for not being very active in the last few months.

No, no need to apologize.

I think we need to come to a shared understanding of what the next steps
are.  Once we have that, we can clarify the current status in the manual
and release announcement, and open issues so that anyone who’d like to
contribute knows where to look at.

> I think one of the problems is that there is not really any style guide
> for now to write services (I do have a WIP patch in my local tree that
> will document most of (gnu services configuration) though :-)).

I see you’ve sent it in the meantime, neat!

> We also lack a way to properly test home services; we would need
> something similar to what Nix Home-manager has[1][2].
>
> [1]: Nix code for configuring a program
> <https://github.com/nix-community/home-manager/blob/master/tests/modules/programs/git/git.nix>
> [2]: Expected content of the serialized configuration
> <https://github.com/nix-community/home-manager/blob/master/tests/modules/programs/git/git-expected.conf>

OK.  Given that ‘define-configuration’ works at a “meta” level, I wonder
if we could have tests that are less boring than this.

Thanks,
Ludo’.


  parent reply	other threads:[~2021-12-20 22:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 17:59 SSH service for Guix Home Ludovic Courtès
2021-12-16 15:43 ` Andrew Tropin
2021-12-20 22:20   ` Ludovic Courtès
2021-12-17 14:21 ` Xinglu Chen
2021-12-20 10:40   ` Andrew Tropin
2021-12-22  7:42     ` Xinglu Chen
2021-12-20 22:31   ` Ludovic Courtès [this message]
2021-12-22  7:43     ` Xinglu Chen

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=87ilvidi35.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andrew@trop.in \
    --cc=guix-devel@gnu.org \
    --cc=public@yoctocell.xyz \
    /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).