From: Attila Lendvai <attila@lendvai.name>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: Shepherd service logging
Date: Tue, 05 Dec 2023 15:39:51 +0000 [thread overview]
Message-ID: <IwB4rlygE9xRDPynMwZ26VwKi9YjFiqHIjyvkuJhXE42iyxQeV1wxJ0NFt6k3XRhUh787sNvTgiqG6KQFSu9gfqlCsDjiOKzaqr-aMN5Xmk=@lendvai.name> (raw)
In-Reply-To: <8734whmth1.fsf@lease-up.com>
> Thanks for offering a logging facility! I run a custom Guix and would
> like to test your changes. Is it enough to switch to your 'wip-logging'
> branch in the package declaration? [1] Thanks!
AFAIU that will lead to quite some local recompiling that are not necessary. you can just set the shepherd package of the shepherd-root-service-type to a custom package.
e.g. this will use the latest shepherd from the shepherd channel:
(operating-system
...
(essential-services
(modify-services (operating-system-default-essential-services
this-operating-system)
(shepherd-root-service-type
config =>
(shepherd-configuration
(inherit config)
(shepherd (@ (shepherd-package) shepherd)))))))
HTH,
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“[A] Computer [programming] language is inherently a pun — [it] needs to be interpreted by both men & machines.”
— Henry Baker
next prev parent reply other threads:[~2023-12-05 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 22:50 Shepherd service logging Ludovic Courtès
2023-12-04 23:35 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-05 15:39 ` Attila Lendvai [this message]
2024-04-18 9:43 ` No public interface for shepherd-package (Was: Shepherd service logging) Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-04-19 20:14 ` No public interface for shepherd-package Ludovic Courtès
2024-04-21 16:13 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
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='IwB4rlygE9xRDPynMwZ26VwKi9YjFiqHIjyvkuJhXE42iyxQeV1wxJ0NFt6k3XRhUh787sNvTgiqG6KQFSu9gfqlCsDjiOKzaqr-aMN5Xmk=@lendvai.name' \
--to=attila@lendvai.name \
--cc=felix.lechner@lease-up.com \
--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).