Pramod V U writes:
But this SUPPORTS broker without systemd. THE "launcher"
USEFLAG...
Yes, dbus-daemon is sufficient, but I'd like to give the choice
for
those who want it.
I repat once again, USE=-launcher will kill off systemd on that
package. Read the output
carefully. "sys-apps/dbus-br
> I am not sure I understand the proposal either, tbh.
Read below to understand
> Although in general, the job of an ebuild tends to be to ensure that
> mandatory requirements are satisfied somehow, so if 66 needs a launcher
> and provides its own (?) then adding a dependency on an external one
Pramod V U writes:
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
Pramod V U 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-l
> The bot(s) also link to
>
> https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide
>
> If you are not a Gentoo Developer, you need a Gentoo Developer to merge
> changes for you. This is called proxying -- you author the change and
> someone else helps you by merging it.
>
> The Pr
> You are right, i was wrong - sorry. i was confused by what you had
> written previously, as in your previous messages, you didn't
> simply write:
>
> By setting USE=-launcher for dbus-broker, systemd doesn't get
> pulled in.
Exactly; However, some evaluation needed on how to handle this for u
On 4/2/25 8:27 PM, Alexis wrote:
>
> Pramod V U writes:
>
>> But this SUPPORTS broker without systemd. THE "launcher" USEFLAG...
>> Yes, dbus-daemon is sufficient, but I'd like to give the choice for
>> those who want it.
>> I repat once again, USE=-launcher will kill off systemd on that
>> pack
> Firstly, as some context, i'm the author of a guide "D-Bus: The
> essentials":
>
> https://github.com/flexibeast/guides/blob/master/dbus.md
>
> and a guide "D-Bus and X sessions":
>
> https://github.com/flexibeast/guides/blob/master/dbus-and-x-sessions.md
>
> as well as having made various ed
> > > 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
> 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 elo
Pramod V U 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
di
66 is an excellent service management suite which uses s6 under the hood,
provides a simple declarative INI format for services, manages dependency
without races, handles logging with s6-log such that logs from different
services stay separate, and makes sure that no line of logs is lost in the
On 4/1/25 11:45 AM, Pramod V U wrote:
> [What's the proxy-maint thing that the QAreport complains? Plz, IDK
> what it is.]
The bot(s) also link to
https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide
If you are not a Gentoo Developer, you need a Gentoo Developer to merge
changes fo
13 matches
Mail list logo
