<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Sep 15, 2014 at 3:17 PM, Marko Käning <span dir="ltr"><<a href="mailto:MK-MacPorts@techno.ms" target="_blank">MK-MacPorts@techno.ms</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>according to this:</div><div>---</div><div><div style="margin:0px;font-size:11px;font-family:Menlo">$ port notes kdelibs4</div><div style="margin:0px;font-size:11px;font-family:Menlo">kdelibs4 has the following notes:</div><div style="margin:0px;font-size:11px;font-family:Menlo"> Don't forget that dbus needs to be started as the local user (not with sudo) before any KDE programs will launch.</div><div style="margin:0px;font-size:11px;font-family:Menlo"> To start it run the following command:</div><div style="margin:0px;font-size:11px;font-family:Menlo"> launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist</div><div style="margin:0px;font-size:11px;font-family:Menlo"> An agent to provide communication between KDE programs must be started.</div><div style="margin:0px;font-size:11px;font-family:Menlo"> To start it run the following command:</div><div style="margin:0px;font-size:11px;font-family:Menlo"> launchctl load -w /Library/LaunchAgents/org.macports.kdecache.plist</div></div><div>---</div><div>it is NOT needed to start any launch *daemon* anymore, the agents are enough!</div></div><div></div></blockquote></div><br>kdelibs4 never had any launch daemons. dbus has both a daemon and an agent, and `port notes kdelibs4` will not display notes for the dbus port.</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra"> pyanfar:2478 Z$ port notes dbus</div><div class="gmail_extra"> dbus has the following notes:</div><div class="gmail_extra"> ############################################################################</div><div class="gmail_extra"> # Startup items have been generated that will aid in</div><div class="gmail_extra"> # starting dbus with launchd. They are disabled</div><div class="gmail_extra"> # by default. Execute the following commands to start them,</div><div class="gmail_extra"> # and to cause them to launch at startup:</div><div class="gmail_extra"> #</div><div class="gmail_extra"> # sudo launchctl load -w</div><div class="gmail_extra"> /Library/LaunchDaemons/org.freedesktop.dbus-system.plist</div><div class="gmail_extra"> # launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist</div><div class="gmail_extra"> ############################################################################</div><div><br></div><div>Note that the inclusion of both means that it's not trying to use the `port load` mechanism, possibly because of confusion.</div><div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>