> 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. > i don't understand why you're talking about elog in the context of > D-Bus. Could you please elaborate? I am asking whether to inform users via `elog "blah blah"` in the ebuild. I have decided to do so. > (My experience is that people regularly fail to distinguish > between a D-Bus system bus - provided by the `dbus` service - > and a D-Bus session bus; each has its own purpose.) This isn't the case here. `66-dbus-launch` supports both. I am just talking about the binary. I will see the packaging of initscripts for the 2 buses once 66 is into the repos. > https://archives.gentoo.org/gentoo-user/87cyeb2gxs....@gmail.com/ > > although i see that Eli has written an overview of the topic in > his reply to you. Thanks Pramod
