Bug 54321 - State Requests and Contacts are core
Summary: State Requests and Contacts are core
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL: http://cgit.collabora.com/git/user/xc...
Whiteboard: r+
Keywords: patch
Depends on:
Blocks: tp-glib-1.0
  Show dependency tree / graph
 
Reported: 2012-08-31 12:55 UTC by Jonny Lamb
Modified: 2012-09-13 08:27 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Jonny Lamb 2012-08-31 12:55:19 UTC 
We should mention this in the spec, and add a critical in tp-glib.
Comment 1 Xavier Claessens 2012-08-31 13:02:25 UTC 
I would consider this as dup of bug #50093
Comment 2 Jonny Lamb 2012-08-31 13:07:51 UTC 
(In reply to comment #1)
> I would consider this as dup of bug #50093

I wouldn't. Merging said interfaces into Connection is a reaaal hassle with no real gain. This is just a change to an assumption.
Comment 3 Xavier Claessens 2012-08-31 13:12:35 UTC 
Fair enough. I would close bug #50093 as WONTFIX then. Ok?
Comment 4 Jonny Lamb 2012-08-31 13:25:28 UTC 
(In reply to comment #3)
> Fair enough. I would close bug #50093 as WONTFIX then. Ok?

It's probably something we'd like to do in the future, but tbh we have enough on our plate as it is. Perhaps just remove the tp-spec-1.0 blocking bug status?
Comment 5 Xavier Claessens 2012-08-31 13:33:35 UTC 
+1
Comment 6 Xavier Claessens 2012-09-06 08:18:32 UTC 
The spec already mention they are mandatory. So this just needs check in Tp(Base)Connection.
Comment 7 Xavier Claessens 2012-09-06 09:41:36 UTC 
Here is the branch: http://cgit.collabora.com/git/user/xclaesse/telepathy-glib.git/log/?h=next-conn-core
Comment 8 Guillaume Desmottes 2012-09-13 08:09:46 UTC 
++
Comment 9 Xavier Claessens 2012-09-13 08:27:44 UTC 
thx, merged.

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.