Hello Hilton,
Hilton Chain <hako@ultrarare.space> writes: > > 2. Need of manually exposing interfaces. e.g. those from shepherd-service. > I feel like this has been a topic mentioned multiple times in the last few weeks on this mailing list. Here I have e-mail from Carlo Zancanaro in mind, "Configuring shepherd services belonging to system services" (I don't know how to 'mention' e-mails in a good way, if you have tips, please do share them), where also this patch https://issues.guix.gnu.org/27155 has been mentioned. I think it's a pity we don't have a generic solution merged yet, especially given the patch that is 8 years old and Ludo mentions in it "It was long overdue.", I agree. The general finalizer approach would allow for exposing further procedures that would alter the services after they are made, things like this would become possible to do easily and we could build on it further, functions like '(finalize-shepherd-service "service" (lambda (config) (.. (inherit (config)))))' and more specific ones like (shepherd-override-auto-start? #f)'. Regards, Rutherther
