Patches welcome, I'd be happy to review this.

(In reply to comment #0)
> It would be useful for telepathy-mission-control to know when a new service
> (like a connection manager or a client) has been installed or removed.
> 
> <smcv> I'd personally spec it as ActivatableServiceAdded(s:
> Well_Known_Name), ActivatableServiceRemoved(s: Well_Known_Name)

Should be ActivatableServiceAdded(as: Array_of_Well_Known_Name), ActivatableServiceRemoved(as: Array_of_Well_Known_Name)?

(In reply to comment #2)
> (In reply to comment #0)
> > <smcv> I'd personally spec it as ActivatableServiceAdded(s:
> > Well_Known_Name), ActivatableServiceRemoved(s: Well_Known_Name)
> 
> Should be ActivatableServiceAdded(as: Array_of_Well_Known_Name),
> ActivatableServiceRemoved(as: Array_of_Well_Known_Name)?

How often do you add/remove more than one activatable service at the same time?

If dbus-daemon detects that one activatable service has been added/removed, how can it know whether there are more to come as part of the same "transaction" (e.g. installing a RPM/dpkg/... package that provides multiple .service files), or whether we've seen the whole "transaction"?

(My guessed answers are "rarely" and "it can't know that, inotify tells us about one file at a time", which is why I didn't suggest "plural" signals.)

If I'm wrong about those and you *can* make "plural" signals work well, the name should be plural too: ActivatableServicesAdded(as), ActivatableServicesRemoved(as).

One way to make them work as "plural" might be to have inotify just trigger a general reload, remember the old set of activatable services before the reload, and do a "diff" operation afterwards.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus/issues/64.