From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 55898@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#55898: Services depending on new Shepherd features may fail until reboot
Date: Tue, 30 Aug 2022 15:50:48 +0200 [thread overview]
Message-ID: <87fshdyh53.fsf@gnu.org> (raw)
In-Reply-To: <c908b6d8-49ce-0eb4-ebe1-011e3c11699c@telenet.be> (Maxime Devos's message of "Tue, 30 Aug 2022 11:35:34 +0200")
Maxime Devos <maximedevos@telenet.be> skribis:
> On 30-08-2022 09:33, Ludovic Courtès wrote:
>
>> So are you suggesting replacing:
>>
>> (defined? 'make-inetd-constructor)
>>
>> by something like:
>>
>> (version<? shepherd-version "0.9.0")
>>
>> or is it something different that you have in mind?
>>
>> I’m not sure how this could improve the user experience, unless by
>> “user” you mean the person writing the service?
>
> (defined? '...) does not work in all contexts -- it works on the
> top-level, but not always inside a procedure, as it tests if the thing
> is defined in (current-module), and not whether it is defined in the
> module that calls (defined? '...).
Right, but that’s a bit of a theoretical concern in my view.
Alternatively, one could write:
(module-defined? (resolve-interface '(shepherd service))
'make-inetd-constructor)
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-08-30 13:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 5:53 bug#55898: jami service failing following 'guix deploy' update Maxim Cournoyer
2022-06-11 14:51 ` Maxime Devos
2022-06-14 19:40 ` Maxim Cournoyer
2022-06-24 17:52 ` Maxim Cournoyer
2022-06-24 18:01 ` bug#55898: jami service failing following reconfigure Maxim Cournoyer
2022-07-06 21:38 ` bug#55898: jami service failing following 'guix deploy' update Maxim Cournoyer
2022-07-06 22:01 ` Maxim Cournoyer
2022-07-20 21:19 ` bug#55898: Services depending on new Shepherd features may fail until reboot Ludovic Courtès
2022-07-21 4:10 ` Maxim Cournoyer
2022-08-29 13:43 ` Ludovic Courtès
2022-08-29 21:06 ` Maxim Cournoyer
2022-08-30 7:33 ` Ludovic Courtès
2022-08-30 9:35 ` Maxime Devos
2022-08-30 13:50 ` Ludovic Courtès [this message]
2022-09-01 13:18 ` Maxim Cournoyer
2022-09-01 13:28 ` Maxime Devos
2022-09-01 13:51 ` Ludovic Courtès
2022-09-01 19:16 ` Maxim Cournoyer
2022-09-02 9:10 ` 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
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=87fshdyh53.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=55898@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=maximedevos@telenet.be \
/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).