From mboxrd@z Thu Jan 1 00:00:00 1970 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: streaksu Newsgroups: comp.lang.ada Subject: Re: systemd controversy Date: Tue, 19 Mar 2024 01:36:20 +0100 Organization: A noiseless patient Spider Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Tue, 19 Mar 2024 00:36:20 -0000 (UTC) Injection-Info: dont-email.me; posting-host="eaa316c221a00dd10213b45fae47a482"; logging-data="492417"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19cyh3qkafqtm5y/5qyWUktSmdtSjH63Lc=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:2EVqpy2crBzg1uitwnSbZe912Uk= Content-Language: en-US In-Reply-To: Xref: news.eternal-september.org comp.lang.ada:66141 List-Id: On 3/18/24 20:56, Lawrence D'Oliveiro wrote: > I was thinking more about code being written for in-house use by > particular customers--I should have made that clear. That is fair enough. > However, what you say is true for open-source code that is being > published. Though I suspect it would still be helpful to provide some info > about how interlocking processes are supposed to fit together, and > systemd .service files could serve as a lingua franca for that, even for > distros that don’t use systemd. The declarative systemd unit-file syntax > should be easier to translate to other forms than perhaps going the other > way. I agree that it could be useful for a project to provide some barebones units for that. If you are, for example, a maintainer for devuan (a systemd less debian) I imagine you will appreciate those being there for documentation rather than not.