[Bug 74030] CM should know the account path of its connections

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=74030

Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Whiteboard|                            |review-
         Depends on|                            |71093

--- Comment #3 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
My patch from <https://bugs.freedesktop.org/show_bug.cgi?id=71093#c9>, and my
comment there, should make the MC side a lot easier to get right.

(In reply to comment #0)
> For example offline roster cache (bug #62378) done from the CM should store
> its DB in "~/.cache/telepathy/roster/gabble/jabber/acc0/user at example.com".

OK. I think I'd prefer to shuffle the paths round so the CM comes first. That'd
be really good for AppArmor, SELinux and similar - telepathy-foo could be
confined so it can only write ~/.cache/telepathy/foo and
~/.local/share/telepathy/foo.

We could perhaps even teach MC to delete
XDG_CACHE_HOME/telepathy/$cm/$protocol/$rest and
XDG_DATA_HOME/telepathy/$cm/$protocol/$rest (*after* calling Disconnect) when
it deletes accounts, and we'd automatically have CM data cleaned up without
needing an equivalent of CM.I.ExternalStorage? But we'd still need a
CM.I.ExternalStorage equivalent for the "Haze should be able to have a
persistent directory equivalent to ~/.purple" use-case, because libpurple
shares one directory between all accounts. So we should decide up-front whose
responsibility it is to clean up - MC or CMs - and if it's the CMs, provide API
for MC to call into them.

> Another example is telepathy-logger could also store its logs in similar
> location.

It should probably be somewhere where it won't be deleted with the account, so
XDG_DATA_HOME/telepathy/logger/$cm/$protocol/$rest or something.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.