Code review comment for lp:~michihenning/unity-scopes-api/scope-cache-dir

> 43 + $HOME/.local/share/unity-scopes/leaf-fs/<scope_id>
> 851 + data_dir_ +
> "/leaf-fs/" + scope_id_
>
> The local content template doesn't exist, so there's no need to try to support
> it.

Not sure what you mean here. We have net, fs, and unconfined scopes. All of these can have a scratch area. I'm going by Jamie's comments here: https://bugs.launchpad.net/unity-scopes-api/+bug/1327426

> 42 + $HOME/.local/share/unity-scopes/leaf-net/<scope_id>
>
> Who's responsible for creating this directory? I suppose the leaf could be
> created by the scope itself (does it have permissions to do that?), but the
> parents have to be created by something unconfined, so who's doing it? The
> click hook?

Yes, the directory needs to be created as part of the installation.