From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Seperate init scripts into different package to support different inits officially
Date: Sun, 28 Feb 2021 08:16:11 +0100 [thread overview]
Message-ID: <20210228071611.VAuB8nMrd2VkRNrVo0zhmXtGpAZjUk5QLDtW08Bzi98@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29112@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/29112#issuecomment-787407028
Comment:
IMO Artix's service split is unnecessary and way too complicated. If we want to support multiple inits at the service level, most services already support `runit` and `s6` without changes, and if we ever wanted to support OpenRC (despite giving up on supervision seeming to me like an extremely bad idea overall, so I don't think anyone will), the services could still go in the same package. Users can just take the few more bytes they occupy or add the directories to `noextract=`.
There are people looking into reusing the `void-runit` framework to enable s6 while still taking advantage of the current infrastructure, but it only touches the `void-runit` package and adjacent ones, not every single package.
Void is primarily a runit distro, and we want the maintenance burden (and even mental load on users) to be optimized for that.
prev parent reply other threads:[~2021-02-28 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 5:57 [ISSUE] " gitpubber
2021-02-28 7:05 ` ericonr
2021-02-28 7:05 ` [ISSUE] [CLOSED] " ericonr
2021-02-28 7:16 ` ericonr [this message]
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=20210228071611.VAuB8nMrd2VkRNrVo0zhmXtGpAZjUk5QLDtW08Bzi98@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).