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

> > IMPORTANT: I think this is understood, the confined process will be able to
> > create the '<scope id>' subdirectory (eg, $HOME/.local/share/unity-scopes
> > /leaf-net/<scope_id>), so the scoperunner/API can do that.
>
> This actually wasn't clear, if that's the case, I think the scope itself
> should just try to create / open the dir and use that, then we don't need a
> new config item that would just be deprecated as soon as possible. (and
> scoperegistry can just create the parent dirs unconditionally)

As long as the process creating the $HOME/.local/share/unity-scopes/leaf-net/ is unconfined, it doesn't matter who creates it. However, don't you still need the config item for the API to know what to return to the confined process so it can create $HOME/.local/share/unity-scopes/leaf-net/<scope_id>?