> If finalizations were put to operating system, use case like this might be
> hard to work and support from the other service configurator will be
> necessary.
Would it not be possible to have, in this example, the module that provides the
source hut service also provide a %postfix-integration-
On Tue, Mar 18 2025, Rutherther wrote:
>> As fuel for thought, we have https://issues.guix.gnu.org/27155 from
>> 2017 which creates a finalization mechanism for any service type, but
>> it built on the idea of explicit extension points which would limit
>> what a finalizer can do to whatever a serv
Aha! I get it now, thanks for clarifying.
I am not against anything here, any presented solution in either the issue or
here seems good imo.
Still, I would like to bring one consideration into account in case the
finalization cannot be made from other service. Since you mentioned NixOS, I
will
Hello Carlo,
thank you for tackling this issue,
imo it's a super useful feature to be able to change (shepherd)
services after they are made.
> As fuel for thought, we have https://issues.guix.gnu.org/27155 from 2017
> which creates a finalization mechanism for any service type, but it
> built
On Sun, Mar 02 2025, Carlo Zancanaro wrote:
> Thinking about this some more, I wonder if there's a better way to do
> this than hard-coding this specific option. This seems like a more
> general issue, where someone wants to modify a "hidden" shepherd
> service in some way that's specific to their
