From: Kai Krakow <hurikhan77@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: sans-dbus was: gnome intrusion?
Date: Sun, 20 Nov 2016 19:40:15 +0100 [thread overview]
Message-ID: <20161120194015.3a3bc7fc@jupiter.sol.kaishome.de> (raw)
In-Reply-To: CAGfcS_mO36YvGC9vb0QaH00dgE8x0-wS_+tAPA3EvxUWm3QEoQ@mail.gmail.com
Am Sat, 19 Nov 2016 17:15:27 -0500
schrieb Rich Freeman <rich0@gentoo.org>:
> On Sat, Nov 19, 2016 at 4:59 PM, Tom H <tomh0665@gmail.com> wrote:
> > On Wed, Nov 16, 2016 at 7:47 AM, Miroslav Rovis
> > <miro.rovis@croatiafidelis.hr> wrote:
> >>
> >> Ah, I almost forgot. Gentoo is as default (OpenRC) without dbus!
> >> Have a look:
> >>
> >> https://wiki.gentoo.org/wiki/Comparison_of_init_systems
> >>
> >> There is no D-Bus under "Main dependencies" for OpenRC (I really
> >> like OpenRC...)
> >
> > There's no reason that the fact that OpenRC doesn't depend on dbus
> > should imply that something higher up the stack cannot depend on
> > dbus!
>
> I'd also comment that utilizing dbus and spawning random processes
> that you don't understand are orthogonal issues. Dbus is just an IPC
> mechanism.
It's actually not dbus' fault that at-spi2 is launched... It's just a
side-effect of at-spi2 being an IPC built ontop of dbus.
What I don't like is that at-spi2 launches it's own dbus instance. Why
not just join the bus that's already there?
--
Regards,
Kai
Replies to list-only preferred.
next prev parent reply other threads:[~2016-11-20 18:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 9:32 [gentoo-user] gnome intrusion? Jorge Almeida
2016-11-14 17:37 ` [gentoo-user] " Ian Zimmerman
2016-11-14 19:03 ` Jorge Almeida
2016-11-14 20:37 ` Kai Krakow
2016-11-14 21:49 ` Jorge Almeida
2016-11-14 23:51 ` Kai Krakow
2016-11-16 12:47 ` [gentoo-user] sans-dbus was: " Miroslav Rovis
2016-11-16 18:42 ` Jorge Almeida
2016-11-17 1:48 ` Rich Freeman
2016-11-17 7:56 ` [gentoo-user] " Ian Zimmerman
2016-11-17 9:08 ` Rich Freeman
2016-11-19 9:21 ` Kai Krakow
2016-11-19 19:06 ` Ian Zimmerman
2016-11-19 19:16 ` Rich Freeman
2016-11-19 20:47 ` Ian Zimmerman
2016-11-19 21:07 ` Alan McKinnon
2016-11-19 21:23 ` Ian Zimmerman
2016-11-19 22:34 ` Canek Peláez Valdés
2016-11-19 22:36 ` Alan McKinnon
2016-11-20 0:36 ` Walter Dnes
2016-11-19 21:59 ` [gentoo-user] " Tom H
2016-11-19 22:15 ` Rich Freeman
2016-11-20 18:40 ` Kai Krakow [this message]
2016-11-14 23:38 ` [gentoo-user] " Andrew Tselischev
2016-11-14 23:52 ` Jorge Almeida
2016-11-15 17:39 ` [gentoo-user] " Ian Zimmerman
2016-11-15 19:23 ` Jorge Almeida
2016-11-15 19:32 ` Alan McKinnon
2016-11-15 19:45 ` Jorge Almeida
2016-11-16 2:10 ` [gentoo-user] " Walter Dnes
2016-11-16 7:23 ` Jorge Almeida
2016-11-16 9:08 ` Neil Bothwick
2016-11-16 11:25 ` Jorge Almeida
2016-11-16 20:51 ` [gentoo-user] " Kai Krakow
2016-11-16 21:20 ` Jorge Almeida
2016-11-17 20:42 ` [gentoo-user] " Frank Steinmetzger
2016-11-17 20:49 ` Jorge Almeida
2016-11-17 23:32 ` Frank Steinmetzger
2016-11-14 23:55 ` [gentoo-user] " 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=20161120194015.3a3bc7fc@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