> > > dbus-broker depends on systemd, and you probably don't want 66
> > > to
> > > pull in systemd. :-)
> >
> > Only with the USE=launcher
> > `66-dbus-launch` in `sys-apps/66-tools` provides an alternative
> > "launcher" which doesn't depend on systemd. It instead uses 66.
>
>
> This page says that 66-dbus-launch actually starts dbus-broker,
> which, as i said, depends on systemd:
>
> https://web.obarun.org/software/66-tools/0.1.1.0/66-dbus-launch/
>
> although i acknowledge that page might be out-of-date.
>
> If it's not, what you'll need in this context is something that
> calls dbus-daemon(1), which doesn't depend on
> systemd. dbus-run-session(1), dbus-launch(1), and the `dbus`
> OpenRC service all use dbus-daemon(1).
dbus-daemon is the reference dbus daemon.
dbus-broker is an efficient daemon which does things more performant, and more
reliable in certain scenarios.
It is just a bus, and the rest of the tasks [configuration, systemd-activation,
logging, opening sockets etc...] are done by dbus-broker-launcher, enabled with
USE=launcher.
The latter "launcher" which babysits the broker, is the one responsible for
depending on systemd.
`66-dbus-launch` replaces that part; to use `66` instead.
> > I am asking whether to inform users via `elog "blah blah"` in
> > the
> > ebuild. I have decided to do so.
>
>
> Inform users of what?
That the `66-dbus-launch` binary is meant for starting exclusively dbus-broker,
and `sys-apps/dbus-broker[-launcher]` is systemd-independant, the launcher is
the one which uses systemd, does activation, etc...
`66-dbus-launch` uses 66 instead, but is otherwise very much same.
