Comment 3 for bug 1398998

It supports debian-packaged scopes that are installed in the system directories just fine. I don't think this is a problem with click itself, but with the scoperunner. As it is right now, the scoperunner requires the scope .ini file and .so file to both be in the same directory, and in the case of scopes which are packaged as clicks, only that one directory can be specified as the "scope" in the manifest.json for the package. The hook then creates a symlink to that directory in ~/.local/share/unity-scopes/ from where the scope gets loaded. I think to fix the, the part of the unity-scopes-api code which resolves the path to the .so, will need to support arch-specific sub-directories within the directory that contains the .ini file, or to have multiple .so files in the same directory, each with its target platform as part of the filename.