From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Paul Sopka" <psopka@sopka.ch>,
"supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re[2]: s6/s6-rc policy for Gentoo: config files for service scripts
Date: Thu, 19 Sep 2024 20:47:03 +0000 [thread overview]
Message-ID: <em4dc5676c-5aad-40b5-a8ec-6b81a7ae505c@427e7077.com> (raw)
In-Reply-To: <3b5567f9-04f3-4cbf-a830-6ff9c0e4a190@sopka.ch>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
>The best would probably be for s6-rc-compile to allow for multiple
>definitions of a service,
>letting later definitions override earlier ones, e.g.
>
>s6-rc-compile ${OUTPUT_DB} ${SOURCE_1} ${SOURCE_2}
>
>where seatd-srv in ${SOURCE_2} overrides seatd-srv in ${SOURCE_1}.
>
>Would this be realizable Laurent?
>
Overrides? No, this would make things confusing and error-prone. The
behaviour
of a set of source definition directories should not be influenced by
whether or not
you're compiling it with another set.
Organizing services is something I don't have a lot of policy advice
on. There's a balance
to be found between ease of use and flexibility; a sound approach seems
to be to have
the service itself hardcoded in the system set of source definition
directories (handled
by the package manager) but keep the run script itself pretty
configurable via
environment definitions sourced from user-modifiable files in /etc. It's
not the only
possible approach, but it works for most services.
--
Laurent
next prev parent reply other threads:[~2024-09-19 20:47 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
2024-09-19 19:07 ` Paul Sopka
2024-09-19 20:47 ` Laurent Bercot [this message]
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=em4dc5676c-5aad-40b5-a8ec-6b81a7ae505c@427e7077.com \
--to=ska-supervision@skarnet.org \
--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).