all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Abbé <gnu.bonfire@p.atriar.ch>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Running guix home + shepherd in non-Guix OS
Date: Mon, 12 Feb 2024 20:43:49 +0000	[thread overview]
Message-ID: <170777063878.7.2894055959768445704.266042677@p.atriar.ch> (raw)
In-Reply-To: <878r3xixcm.fsf@zancanaro.id.au>


[-- Attachment #1.1: Type: text/plain, Size: 1049 bytes --]

Hi Carlo,

Apologies for missing your reply, and thank you for time to reply to me.

On Tuesday, February 6th, 2024 at 1:35 PM, Carlo Zancanaro <carlo@zancanaro.id.au> wrote:

> Hi Abbé,
> 

> On Mon, Feb 05 2024, Abbé wrote:
> 

> > I'm wondering how would one go about integrating shepherd with 'guix
> > home' configuration (i.e. home environment services), akin to what
> > Guix does (I believe, without needing to do 'guix home ...').

[...]
 

> Guix Home does more than just start shepherd services. It is a system
> for managing packages, configuration files, etc. If you haven't already,
> I would suggest reading "(guix) Home Configuration" in the manual.

Thanks, on careful reading, I spotted what I was missing. It works as expected now.

> 

> There isn't really anything that you can put into your Shepherd config
> to execute your Home configuration. It goes the other way: instantiating
> your Home config will start a Shepherd process.
> 

> I hope that helps,
> 

> Carlo

Thanks!
--
Abbé

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

      reply	other threads:[~2024-02-12 20:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 15:00 Running guix home + shepherd in non-Guix OS Abbé
2024-02-06 12:35 ` Carlo Zancanaro
2024-02-12 20:43   ` Abbé [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

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

  git send-email \
    --in-reply-to=170777063878.7.2894055959768445704.266042677@p.atriar.ch \
    --to=gnu.bonfire@p.atriar.ch \
    --cc=carlo@zancanaro.id.au \
    --cc=help-guix@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 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.