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

[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]

Hi,

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.  :-)

> Also, could you (or Xinglu, or Oleg) write a blog post for
> guix.gnu.org, targeting an audience who’s not familiar with this kind
> of tool, making it clear what the rationale is and what it can bring
> to “normal users”?  It would be really helpful to have that published
> within a couple of weeks or so, before the next release.

That sounds like a good idea, I would be happy to help!

> 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.

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 :-)).  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>


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  parent reply	other threads:[~2021-12-17 14:22 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 [this message]
2021-12-20 10:40   ` Andrew Tropin
2021-12-22  7:42     ` Xinglu Chen
2021-12-20 22:31   ` Ludovic Courtès
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=877dc3jor3.fsf@disroot.org \
    --to=public@yoctocell.xyz \
    --cc=andrew@trop.in \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).