touch-packages team mailing list archive

[Rodney Dawes <1398998@xxxxxxxxxxxxxxxxxx>]

On Fri, 2014-12-05 at 03:44 +0000, Michi Henning wrote:
> Not sure what you mean by "it", click or unity-scopes-api? Presumably,
> unity-scopes-api?

Sorry, yes, 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.

But this is only valid for scopes which are not packaged as clicks. For
scopes packaged as clicks, you can only have on directory with one .ini
file and one .so in it. Also, the .ini file is not architecture
dependent, so having to include N exact copies of the file in different
locations, just for different architectures, seems like a bad solution.
The scope cannot be installed in three different places from click
packages right now. The hook only supports one scope directory. Thus, it
only supports one architecture per click package. This is the problem.

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

I don't think this is a problem with the manifest. Unless you're
suggesting that the way hooks work needs to be changed, but this still
would require changes on the unity-scopes-api side.

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