From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from alyss.skarnet.org (alyss.skarnet.org [95.142.172.232]) by inbox.vuxu.org (Postfix) with SMTP id C5B7021581 for ; Thu, 19 Sep 2024 22:47:08 +0200 (CEST) Received: (qmail 5184 invoked by uid 89); 19 Sep 2024 20:47:34 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 5176 invoked from network); 19 Sep 2024 20:47:34 -0000 From: "Laurent Bercot" To: "Paul Sopka" , "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 Message-Id: In-Reply-To: <3b5567f9-04f3-4cbf-a830-6ff9c0e4a190@sopka.ch> References: <442f0112-3120-4609-8a87-c4d9f7119868@sopka.ch> <3b5567f9-04f3-4cbf-a830-6ff9c0e4a190@sopka.ch> Reply-To: "Laurent Bercot" User-Agent: eM_Client/10.0.3530.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------=_MBA41DA9BD-2EED-4049-9C3C-CF649C9F2C29" --------=_MBA41DA9BD-2EED-4049-9C3C-CF649C9F2C29 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable >The best would probably be for s6-rc-compile to allow for multiple=20 >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=20 behaviour of a set of source definition directories should not be influenced by=20 whether or not you're compiling it with another set. Organizing services is something I don't have a lot of policy advice=20 on. There's a balance to be found between ease of use and flexibility; a sound approach seems=20 to be to have the service itself hardcoded in the system set of source definition=20 directories (handled by the package manager) but keep the run script itself pretty=20 configurable via environment definitions sourced from user-modifiable files in /etc. It's=20 not the only possible approach, but it works for most services. -- Laurent --------=_MBA41DA9BD-2EED-4049-9C3C-CF649C9F2C29--