<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - sd-daemon.c: should be possible to avoid mq support and hence -lrt dependency" href="https://bugs.freedesktop.org/show_bug.cgi?id=63167#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - sd-daemon.c: should be possible to avoid mq support and hence -lrt dependency" href="https://bugs.freedesktop.org/show_bug.cgi?id=63167">bug 63167</a> from <a class="email" href="mailto:simon.mcvittie@collabora.co.uk" title="Simon McVittie <simon.mcvittie@collabora.co.uk>"> Simon McVittie</a> <pre>(In reply to <a href="show_bug.cgi?id=63167#c1">comment #1</a>) > a nicer alternative would be to change dbsu to actually > link dynamically against libsystem-daemon.so Yeah, I did consider it. At the moment I believe dbus can accept the systemd LISTEN_FDS protocol (which is, admittedly, hardly rocket science) without actually being linked against libsystemd-daemon; so this would be a small feature regression. I've actually considered turning dbus-launch into a two-stage thing - listen on the socket, then start dbus-daemon when its activation environment is ready and use the LISTEN_FDS protocol to give it the socket - to avoid bugs like <<a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682375">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682375</a>> without necessarily needing systemd --user. (I realise your answer is going to be "use systemd --user then".)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>