From: Jan Braun <janbraun@gmx.de>
To: Paul Sopka <psopka@sopka.ch>
Cc: supervision@list.skarnet.org
Subject: Re: s6/s6-rc policy for Gentoo: config files for service scripts
Date: Fri, 20 Sep 2024 13:10:30 +0200 [thread overview]
Message-ID: <Zu1YJuzw6qRv25Fd@abakus> (raw)
In-Reply-To: <38e6d7af-8111-425e-b5d3-9f8933d54723@sopka.ch>
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
Paul Sopka schrob:
> I do not think that providing only this option this is a good idea,
> since names are unique and dependencies are declared in the dependent
> service.
"It simplifies dependencies" sounds like a good reason to go with the
tryexec approach.
Cheers,
Jan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-20 11:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 19:43 Paul Sopka
2024-09-19 3:33 ` Jan Braun
2024-09-19 14:40 ` Paul Sopka
2024-09-19 17:51 ` Jan Braun
2024-09-19 18:28 ` Hoël Bézier
2024-09-19 19:11 ` Paul Sopka
2024-09-19 20:26 ` Jan Braun
2024-09-20 10:19 ` Paul Sopka
2024-09-20 11:10 ` Jan Braun [this message]
2024-09-19 19:07 ` Paul Sopka
2024-09-19 20:47 ` Re[2]: " Laurent Bercot
2024-09-20 10:21 ` Paul Sopka
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zu1YJuzw6qRv25Fd@abakus \
--to=janbraun@gmx.de \
--cc=psopka@sopka.ch \
--cc=supervision@list.skarnet.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.
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 NNTP newsgroup(s).