public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] rfc: making sysvinit optional
Date: Thu, 11 Jul 2019 11:39:10 -0400	[thread overview]
Message-ID: <CAJ0EP41AVVOUjQ8=HSmSwHHj-OdKsNdat7RYnvKzmFZFaGJ6gA@mail.gmail.com> (raw)
In-Reply-To: <20190711030207.GA23937@linux1.home>

On Wed, Jul 10, 2019 at 11:02 PM William Hubbs <williamh@gentoo.org> wrote:
> > Systemd already has IUSE=+sysv-utils which has a similar function:
> > [-      ] sysv-utils
> >     sys-apps/systemd: Install sysvinit compatibility symlinks and
> >     manpages for init, telinit, halt, poweroff, reboot, runlevel, and
> >     shutdown
>
> Actually, I like the name sysv-utils for this use flag; that seems to
> describe better what it does.
>
> > RDEPEND="sysv-utils? ( !sys-apps/sysvinit )
> >          !sysv-utils? ( sys-apps/sysvinit )"
>
>  I like this, but the second branch (!sysv-utils) is not really needed,
>  because if we put sysvinit as the first RDEPEND of virtual/init, we
>  don't need to worry about installing it through rdepend in openrc.

To clarify why this strange looking dependency is there in
sys-apps/systemd: I felt it was fairly important to always have init,
shutdown, etc. available to avoid breaking other tools and to prevent
confusion. systemd is technically usable without them, but you would
need to explicitly set up your bootloader to add
init=/lib/systemd/systemd to the kernel command line, and you would
need to call systemctl directly instead of using the symlinks to shut
the system down.

Relying on any-of dependency ordering in a virtual package to
accomplish this is a bit optimistic. That can go wrong easily if the
user installs multiple providers.

> We can also add sys-apps/openrc as an rdepend of sys-apps/sysvinit possibly.

Please do not do this without consulting me first. This could
introduce a dependency conflict in sys-apps/systemd.


  parent reply	other threads:[~2019-07-11 15:39 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
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 [this message]
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='CAJ0EP41AVVOUjQ8=HSmSwHHj-OdKsNdat7RYnvKzmFZFaGJ6gA@mail.gmail.com' \
    --to=floppym@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