GNU bug report logs - #69591
[PATCH 00/31] Unbundle and update python-pytorch

Previous Next

Full log

Message #416 received at 69591 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 71739 <at> debbugs.gnu.org, 69591 <at> debbugs.gnu.org,
 David Elsing <david.elsing <at> posteo.net>, Matthew Trzcinski <matt <at> excalamus.com>,
 Florian Pelz <pelzflorian <at> pelzflorian.de>
Subject: Re: [bug#69591] [PATCH] services: shepherd: Support
 “free-form” services.
Date: Mon, 24 Jun 2024 23:22:33 -0400

Hi Ludovic,

Ludovic Courtès <ludo <at> gnu.org> writes:

[...]

>> Hm, if free-form is expected to be a built-in procedure provided by
>> Shepherd, should we call it 'built-in' instead of 'free-form' ?
>
> I view it as something more generic: it’s typically, but not just, for
> when the service comes from a procedure defined in the Shepherd itself.
>
> Other use case is when as a service author you need more freedom that
> what you get with the ‘start’ and ‘stop’ fields, like:
>
>   (shepherd-service
>     ;; …
>     (free-from #~(let ((whatever (spawn-fiber …)))
>                    (service '(foo) #:start …))))
>
> It’s probably going to be a relatively marginal use case, but it’s good
> to have that extra level of flexibility.
>
> WDYT?

Thanks for the extra explanation and example.  The extra flexibility
sounds good to me!

Reviewed-by: Maxim Cournoyer <maxim.cournoyer <at> gmail>

-- 
Thanks,
Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.