Pramod V U <pramodvu1...@proton.me> writes:
[Should I depend on dbus-broker[-launcher] when the 66-tools
provides
an alternative launcher by USE=dbus? OR should I let the users
do it
via `elog`? OR should I use some other useflag other than
"dbus"?]
[I've decided to go with the elog approach; might also choose to
disable the dbus part completely... if even that fails]
dbus-broker depends on systemd, and you probably don't want 66 to
pull in systemd. :-)
i don't understand why you're talking about elog in the context of
D-Bus. Could you please elaborate?
You might want to read the D-Bus page on the wiki to get a handle
on D-Bus:
https://wiki.gentoo.org/wiki/D-Bus
(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.)
[What's the proxy-maint thing that the QAreport complains? Plz,
IDK
what it is.]
Just wanted to note that i mentioned being a proxy maintainer in
one of my replies to you in our previous discussion about this
stuff:
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.
Alexis.
