disable/enable apps based on whether the required frameworks are available on image

Bug #1271944 reported by Alexander Sack on 2014-01-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
click (Ubuntu)
Michael Vogt

Bug Description

click apps should be disabled if the required framework is not available on the image. Accordingly apps should be enabled if the required frameworks become available.

This probably involves:
 1. how to disable an app without uninstalling (so if a new/compatible app becomes available in the store, the app is automatically enabled)
 2. how to let the scope know whether an app is "enabled" or "disabled" so it can reflect status properly in the UI.
 3. ensure we trigger check for apps and mark them as disabled on image update and when new app gets downloaded.

Related branches

tags: added: appstore
Colin Watson (cjwatson) on 2014-01-24
Changed in click (Ubuntu):
status: New → Triaged
importance: Undecided → High
description: updated
description: updated
Michael Vogt (mvo) on 2014-05-07
Changed in click (Ubuntu):
status: Triaged → In Progress
Colin Watson (cjwatson) on 2014-05-19
Changed in click (Ubuntu):
assignee: nobody → Michael Vogt (mvo)
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package click -

click ( utopic; urgency=medium

  [ Colin Watson ]
  * chroot: Force dpkg-architecture to recalculate everything rather than
    picking up values from the environment, to avoid the test suite getting
    confused by environment variables exported by dpkg-buildpackage.
  * tox.ini: Regularise whitespace.
  * Lintian complains about dh --with gir without a direct Build-
    Depends: gobject-introspection, although libgirepository1.0-dev
    depends on it. Build-depend on both.
  * Factor out some repetitive PackageKit error-reporting code.
  * Fix test coverage glitch.
  * Avoid ensure_dbing multiple times.
  * /custom/click, not /custom.
  * Remove trailing whitespace.
  * Document chroot session management.
  * Make manifest.json example actually be valid JSON.
  * Document that click chroot -s is mainly for debugging.
  * Allow specifying a framework base directly.
  * Fix docstring.
  * Add appropriate Since: annotations.
  * formatting
  * merge lp:~mvo/click/documentation-tweak
  * merge lp:~mvo/click/avoid-exposing-envvars

click (0.4.23) utopic; urgency=medium

  [ Michael Vogt ]
  * Show human-readable error message when a click chroot subcommand fails
    because of existing or non-existing chroots (LP: #1296820).
  * Selectively disable logging on some tests to avoid message spam during
    the test runs.
  * When running hooks, remove hook symlinks if framework requirements are
    not met (LP: #1271944).
  * Cleanup the chroot if "click chroot create" fails (unless
    --keep-broken-chroot is used)
  * Fix sources.list generation when native_arch and target_arch are on the
    same archive server (part of LP #1319153).
  * Add "click framework list" command to list available frameworks
    (LP: #1294659).

  [ Pete Woods ]
  * Add libunity-scopes-dev package to chroot (LP: #1320786).

  [ Sergio Schvezov ]
  * click chroot creation depends on dpkg-architecture, so recommend

  [ Colin Watson ]
  * chroot: Handle the case where we can execute binaries for the target
    architecture directly and thus don't need a cross-compiler
    (LP: #1319153).
 -- Ubuntu daily release <email address hidden> Tue, 20 May 2014 13:15:41 +0000

Changed in click (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers