On May 18, 2011, at 8:45 PM, John Ralls wrote: > The reason for the dbus dance is to provide a drag-and-drop app bundle rather > than an installer. I'm pretty sure that using launchd requires installing > dbus somewhere permanent and setting up a launch daemon for it -- which would > require using an Installer bundle (a .mpkg) instead. >
I don't think that's true. You can still install it with drag and drop. You
can put the dbus binary anywhere and simply put a symlink to the plist in the
LaunchAgents directory as my script changes do. Give it a try and I think
you'll see that it works. If not I'll try to fix it so it does. You might
have to change the plist itself to point to the dbus server, or perhaps put a
symlink to the server somewhere else. So long as the plist points to it,
things should work.
> FWIW, direct use of dbus is now discouraged: One is supposed to use gdbus
> instead, and I've had to hold back the GConf version because recent releases
> do so and there's a race condition in gdbus that prevents it from connecting
> on OSX -- or there was in February when I last looked at it. That aside,
> though, gdbus also provides a hook for a platform-specific dbus replacement.
> I'd like to do one for OSX using NSUserDefaults and NSNotifications, which
> would eliminate the need for a dbus daemon entirely. Finding time to do that
> is a bit of a rub, though.
Fine, but in the meantime, I think this would be an improvement.
Mike
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
