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>
Cc: Guix Devel <guix-devel@gnu.org>, Andrew Tropin <andrew@trop.in>
Subject: Re: SSH service for Guix Home
Date: Wed, 22 Dec 2021 08:43:20 +0100	[thread overview]
Message-ID: <87mtktw0dj.fsf@yoctocell.xyz> (raw)
In-Reply-To: <87ilvidi35.fsf@gnu.org>

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

Hi,

Am Montag, der 20. Dezember 2021, um 23:31 +012, schrieb Ludovic Courtès <ludo@gnu.org>:

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

Yeah, maybe we could create a bug report listing all the things that
should be done/fixed before we start adding too many new home services?

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

Andrew also sent a patch that provides some guidelines for how to write
services[1], in case you haven’t seen it already.

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

What exactly do you mean by “meta” level?  Do you have anything
particular in mind regarding the tests?

[1]: <https://yhetil.org/guix-patches/87h7b2b6n3.fsf@trop.in/>

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

      reply	other threads:[~2021-12-22  7:50 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
2021-12-22  7:43     ` Xinglu Chen [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=87mtktw0dj.fsf@yoctocell.xyz \
    --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).