Pramod V U <pramodvu1...@proton.me> writes:
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).
I am asking whether to inform users via `elog "blah blah"` in
the
ebuild. I have decided to do so.
Inform users of what?
Alexis.
