From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: making sysvinit optional
Date: Wed, 10 Jul 2019 19:30:57 -0400 [thread overview]
Message-ID: <45d06884-b97c-6bcc-f254-93a5e6eb5f57@gentoo.org> (raw)
In-Reply-To: <20190710231614.GA3597@whubbs1.dev.av1.gaikai.org>
On 7/10/19 7:16 PM, William Hubbs wrote:
> 3. add a sysvinit use flag to openrc, which will be off by default. When
> it is on, openrc will block sysvinit since it will provide /sbin/init
> and /sbin/shutdown.
>
This logic, or maybe the name of the flag, sounds backwards to me. I
only get sysvinit when USE=sysvinit is NOT set?
> RDEPEND="
> kernel_linux? (
> || (
> sys-apps/sysvinit
> sys-apps/systemd
> sys-apps/openrc
> sys-process/runit
> virtual/daemontools
> )
Modulo my first comment, you'll want some USE flag (un)set for
sys-apps/openrc to ensure that /sbin/init is provided.
next prev parent reply other threads:[~2019-07-10 23:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 20:25 [gentoo-dev] rfc: making sysvinit optional William Hubbs
2019-07-10 21:48 ` William Hubbs
2019-07-10 23:16 ` William Hubbs
2019-07-10 23:30 ` Michael Orlitzky [this message]
2019-07-11 0:03 ` William Hubbs
2019-07-11 0:17 ` Michael Orlitzky
2019-07-11 3:14 ` William Hubbs
2019-07-11 13:01 ` Michael Orlitzky
2019-07-11 15:43 ` William Hubbs
2019-07-11 16:11 ` Michael Orlitzky
2019-07-11 17:03 ` William Hubbs
2019-07-11 0:17 ` Rich Freeman
2019-07-11 3:02 ` William Hubbs
2019-07-11 13:42 ` Rich Freeman
2019-07-11 15:56 ` William Hubbs
2019-07-11 16:46 ` Rich Freeman
2019-07-11 17:22 ` William Hubbs
2019-07-11 17:38 ` Rich Freeman
2019-07-11 15:39 ` Mike Gilbert
2019-07-11 16:43 ` William Hubbs
2019-07-11 0:19 ` William Hubbs
2019-07-13 17:51 ` William Hubbs
2019-07-14 13:54 ` Mike Gilbert
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=45d06884-b97c-6bcc-f254-93a5e6eb5f57@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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