From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [RFC] Seperate init scripts into different package to support different inits officially
Date: Sun, 28 Feb 2021 08:05:20 +0100 [thread overview]
Message-ID: <20210228070520.iTZjF1iMbXQ1XTqbrBYTP5WvTjIwcuDP1F7kzT2mTus@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: 1521 bytes --]
Closed issue by gitpubber on void-packages repository
https://github.com/void-linux/void-packages/issues/29112
Description:
Currently Void Linux only offers Runit init. I want VoidLinux to offer other Init systems too. I am specifically eyeing for s6 .
Currently VoidLinux packages init scripts into package itself. But,i want Voidlinux to pack them into seperate package like what Artix Linux does.
To be more specific, if `packagename` is package, i want `packagename-openrc` , `packagename-runit` , `packagename-s6` too. device using runit would install packagename-runit package and device using s6 would install packagename-s6 package. Thus,we can support different inits officially without any hacks.
You would rebut this method by saying that when a package is installed, init scripts must also be installed automatically. I have solution for that too. a package `packagename` would depend on `packagename-init` . there would be 3 repositories void-openrc , void-runit , void-s6 . if device is using runit,then void-runit repository would be added. if device is using s6 , then void-s6 repository would be added. `packagename-init` package in void-runit would contain runit scripts while `packagename-init` in void-s6 would contain s6 scripts.
At last, i would like to ask you not to reply "All devs use runit,so there is no interest in other inits".I am sure there are many who would like to support other inits. I love void very much and would love void to support other inits officially as well.
next prev parent reply other threads:[~2021-02-28 7:05 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 ` ericonr [this message]
2021-02-28 7:16 ` ericonr
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=20210228070520.iTZjF1iMbXQ1XTqbrBYTP5WvTjIwcuDP1F7kzT2mTus@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).