Code review comment for lp://staging/~ted/libindicator/upstart-no-dbus

> On Wed, 2013-05-29 at 16:18 +0000, Lars Uebernickel wrote:
>
> > All of these things will be true anyway, because upstart *is* managing
> > the services.
>
>
> I guess, but I'm not sure why you're concerned over the job
> configuration having:
>
> start on dbus-activation com.canonical.indicator.network
>
> versus
>
> start on indicators-loaded
>
> It seems like the second one is clearer and can be managed more easily
> as we'll be able to introspect the startup with things like initctl2dot.

My point is that the first one won't be needed. Upstart should just take control over all dbus-activated things in the session.