From: Felix Lechner via <help-guix@gnu.org>
To: Nicolas Odermatt-Lemay <nodermattlemay@gmail.com>, help-guix@gnu.org
Subject: Re: Efficient iterative shepherd service development ?
Date: Mon, 05 Aug 2024 11:36:13 -0700 [thread overview]
Message-ID: <875xsees0y.fsf@lease-up.com> (raw)
In-Reply-To: <CAC-BrWpGxeQJpRSCT3nqn=Z-whjcG+fu1bs7JpzdJod=ELv_zw@mail.gmail.com>
Hi Nicholas,
On Mon, Aug 05 2024, Nicolas Odermatt-Lemay wrote:
> So I'd like to know the "Guix way", or just a more efficient way to do
> this type of development.
I'd use the Shepherd REPL. [1]
You'll have to install the executables you need into the system profile,
since their store paths may not be known inside the REPL.
Kind regards
Felix
[1] https://www.gnu.org/software/shepherd/manual/html_node/REPL-Service.html
next prev parent reply other threads:[~2024-08-05 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 4:06 Efficient iterative shepherd service development ? Nicolas Odermatt-Lemay
2024-08-05 18:36 ` Felix Lechner via [this message]
2024-08-07 9:05 ` Carlo Zancanaro
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=875xsees0y.fsf@lease-up.com \
--to=help-guix@gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=nodermattlemay@gmail.com \
/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.
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).