Bug 13130

Summary: CMs without .manager files should be queried for the protocols they support
Product: Telepathy Reporter: Will Thompson <will>
Component: libtelepathyAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED WONTFIX QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Will Thompson 2007-11-07 07:33:36 UTC 
telepathy-haze currently ships a .manager file that may or may not contain an accurate list of protocols supported by telepathy-haze on the machine in question under the current phase of the moon.  Only at runtime, when libpurple probes for plugins, is the list known.

There needs to be some way to tell clients to just start up the CM and ask it what it supports rather than relying on the .manager.  One way would be to add a may-be-full-of-lies flag to the .manager.  Rob suggested that a cleaner technique would be for clients to use ListActivatableNames to figure out which CMs are installed, and start and probe those which do not have .manager files.
Comment 1 Simon McVittie 2008-01-28 03:16:46 UTC 
telepathy-glib implements the proposed technique and the spec describes it, so I think we can close this bug when libtelepathy is implemented using telepathy-glib. Reassigning to libtelepathy.
Comment 2 Simon McVittie 2009-09-29 03:35:18 UTC 
libtelepathy is dead. This bug won't be fixed.

(It's fixed in telepathy-glib, though.)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.