public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd
Date: Tue, 22 Dec 2015 00:18:18 +0100	[thread overview]
Message-ID: <20151222001818.56c264b9@jupiter.sol.kaishome.de> (raw)
In-Reply-To: 20151221165939.5f6fa9b8@sepulchrave.remarqs

Am Mon, 21 Dec 2015 16:59:39 -0600
schrieb »Q« <boxcars@gmx.net>:

> On Mon, 21 Dec 2015 21:40:30 +0000
> Neil Bothwick <neil@digimed.co.uk> wrote:
> 
> > On Mon, 21 Dec 2015 16:25:34 -0500, waltdnes@waltdnes.org wrote:
> > 
> > > > From what I read/understand openrc is in the process of removal
> > > > from @system, for all profiles?    
> > > 
> > >   In Lennart's dreams... and many peoples' nightmares.  
> > 
> > It's got nothing to do with Lennart. There is a choice of init
> > managers, openrc or systemd - so portage should, and apparently
> > will, handle this with a virtual. Currently, openrc is forced on
> > those using systemd, even though they have no use for it - that is
> > just as wrong as forcing systemd on openrc users.
> 
> AFAICT, the day is pretty close.
> 
> <https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/profiles/base/packages>
> and <https://bugs.gentoo.org/show_bug.cgi?id=511500> indicate openrc
> is still in @system as a stopgap, to keep providing functions.sh
> because of bugs 373219 (FIXED already) and
> <https://bugs.gentoo.org/show_bug.cgi?id=504116>, which only has 4
> ebuilds left to fix.

Fixed here by install masking /etc/init.d and symlinking functions.sh
to the new location. ;-)

Disclaimer: Do not apply on openrc systems.

-- 
Regards,
Kai

Replies to list-only preferred.




  reply	other threads:[~2015-12-21 23:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20 18:26 [gentoo-user] Problem with openrc-0.18.4 and ifplugd Mick
2015-12-21  1:29 ` thelma
2015-12-21  6:15   ` Mick
2015-12-21 14:06     ` [gentoo-user] " James
2015-12-21 17:21       ` Peter Humphrey
2015-12-21 20:33         ` Alan McKinnon
2015-12-21 20:30       ` Alan McKinnon
2015-12-21 21:25       ` waltdnes
2015-12-21 21:40         ` Neil Bothwick
2015-12-21 22:59           ` »Q«
2015-12-21 23:18             ` Kai Krakow [this message]
2015-12-21 21:43         ` Kai Krakow
2015-12-21 22:37           ` Mick
2015-12-21 22:38             ` Alan McKinnon
2015-12-21 23:20               ` Mick
2015-12-21 23:35                 ` Neil Bothwick
2015-12-21 23:55                   ` Mick
2015-12-22  0:48                     ` Neil Bothwick
2015-12-22  0:54                       ` Mick
2015-12-22  1:12                         ` Kai Krakow
2015-12-22 14:04                           ` Mick
2015-12-22 14:20                             ` Kai Krakow
2015-12-22 15:15                               ` Mick
2015-12-22 23:32                                 ` Neil Bothwick
2015-12-23 10:58                                   ` Mick
2015-12-21 23:41                 ` Mick
2015-12-21 23:54                   ` Kai Krakow
2015-12-21 23:49                 ` Kai Krakow
2015-12-22  0:50                   ` Mick
2015-12-22  1:12                     ` Kai Krakow
2015-12-21 22:54             ` Kai Krakow

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=20151222001818.56c264b9@jupiter.sol.kaishome.de \
    --to=hurikhan77@gmail.com \
    --cc=gentoo-user@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