touch-packages team mailing list archive

[Rodney Dawes <1398998@xxxxxxxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to click in Ubuntu.
https://bugs.launchpad.net/bugs/1398998

Title:
  Cannot provide multi-arch click packages for scopes

Status in click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  Currently, click packages with scopes cannot provide the same scope
  for multiple architectures, as the hook takes the directory name that
  the scope is in, but does not support the .so for the scope being in a
  sub-directory based on the arch triplet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1398998/+subscriptions