touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

The .ini file *is* architecture dependent, because it allows a custom
scoperunner to be used, and that scoperunner is architecture dependent.

If click supports only one architecture per package (which strikes me as a
good thing, BTW), that would seem to make it a click issue?
scopes-api doesn't care about *how* things get installed, and it has
nothing to do with the hooks.

Why would we want more than one architecture in a
single click? I'd be downloading a bunch of binaries
(possibly over the cell network) every time I install something. To what end?

As far as unity-scopes-api is concerned, it's entirely fine to have multiple
architectures in the file system. Everything that is architecture dependent
is already in separate locations, so none of the arch-specific files overwrite
each other. So, I just don't see what we would change in scopes-api or how.

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