touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

"It supports debian-packaged scopes that are installed in the system
directories just fine."

Not sure what you mean by "it", click or unity-scopes-api? Presumably,
unity-scopes-api?

The scoperunner expects to be told what the scope's .ini file is. The
.ini file and the .so need to be in the same single directory. That's
it. The scoperunner can deal with different architectures just fine. If
we want to install the same single scope three times for different
architectures on the same machine, that's not a problem: install the
scope three times in three different directories, each containing the
.so and the .ini file.

It seems there is a problem with the manifest for scopes rather than the
scopes run time?

-- 
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