all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Richard Sent <richard@freakingpenguin.com>
Cc: 69781-done@debbugs.gnu.org, paren@disroot.org,
	Tanguy Le Carrour <tanguy@bioneland.org>,
	rustand.lars@gmail.com, Andrew Tropin <andrew@trop.in>
Subject: bug#69781: [PATCH v2] services: Add the Guix Home Service
Date: Wed, 17 Apr 2024 12:18:13 +0200	[thread overview]
Message-ID: <87h6g0i97e.fsf@gnu.org> (raw)
In-Reply-To: <3394b0b51f6a5a608ebcfb7a63fdc34e52fe928e.1711046203.git.richard@freakingpenguin.com> (Richard Sent's message of "Thu, 21 Mar 2024 14:36:43 -0400")

Hi Richard,

Richard Sent <richard@freakingpenguin.com> skribis:

> This patch adds a Guix Home Service, which allows for configuring/deploying an
> operating-system declaration with an associated home-environment.
>
> * gnu/services/guix.scm: Add guix-home-service and guix-home-shepherd-service
> * gnu/home/services/shepherd.scm: Don't attempt to launch user shepherd when
> the system shepherd runs guix-home-<user>
> * doc/guix.texi: Add documentation for guix-home-service
> * gnu/tests/guix.scm: Add a test to verify guix-home-service-type is able to
> activate a home environment
>
> Change-Id: Ifbcc0878d934aa4abe34bb2123b5081fb432aa8e

This addresses a longstanding user request, nice!

I followed up with a doc update to make the service more discoverable.

Thank you!

Ludo’.




  reply	other threads:[~2024-04-17 10:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 18:41 [bug#69781] [PATCH] services: Add the Guix Home Service Richard Sent
2024-03-21 18:36 ` [bug#69781] [PATCH v2] " Richard Sent
2024-04-17 10:18   ` Ludovic Courtès [this message]
2024-04-29 10:14   ` Ludovic Courtès
2024-04-29 13:41     ` Ludovic Courtès
2024-04-29 15:21       ` Richard Sent
2024-05-25 13:04         ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h6g0i97e.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=69781-done@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=paren@disroot.org \
    --cc=richard@freakingpenguin.com \
    --cc=rustand.lars@gmail.com \
    --cc=tanguy@bioneland.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.