Bug 71857 - Add STORAGE_RESTRICTION_FLAG_CANNOT_DELETE
Summary: Add STORAGE_RESTRICTION_FLAG_CANNOT_DELETE
Status: RESOLVED MOVED
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:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-20 23:00 UTC by Xavier Claessens
Modified: 2019-12-03 20:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Xavier Claessens 2013-11-20 23:00:28 UTC
Currently (as in 5.17) MC interprets CANNOT_SET_ENABLED || CANNOT_SET_PRESENCE as if we can't delete the account. I that's unintuitive interpretation of those flags and we should add an explicit one. This is motivated by UOA/GOA use case where the Telepathy account is part of a "bigger" account. If I delete my google telepathy account, that would remove remove from EDS/mails/google-drive/whatever... So I don't think those accounts should be deletable from telepathy stack.
Comment 1 Xavier Claessens 2013-11-20 23:02:18 UTC
And while we are at it, I see that comment in UOA MC plugin:
/* FIXME: We can't set Icon either, but there is no flag for that */
Comment 2 GitLab Migration User 2019-12-03 20:26:52 UTC
-- 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/telepathy/telepathy-spec/issues/145.


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.