Need a mechanism through which to receive snap changes events
Bug #1637404 reported by
Marcus Tomlinson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Confirmed
|
High
|
Alejandro J. Cura | ||
snapd (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Clients such as the snappy store scope / app, and libsnapd-glib/qt need a mechanism through which to receive snap state change signals from snapd (such as install progress, snap installed / uninstalled, etc.).
During the Devices Sprint it was decided that it would be sufficient enough for ALL events to be broadcasted to ALL subscribers. It'd then be left up to the receiving end to ignore those events it wasn't concerned with.
E.g. An event would simply say something along the lines of: “snap X changed from state A to state B”
description: | updated |
summary: |
- Dig up events logic from commit history + Need a mechanism through which to receive snap changes events |
Changed in snapd (Ubuntu): | |
importance: | Undecided → High |
Changed in canonical-devices-system-image: | |
assignee: | nobody → Pat McGowan (pat-mcgowan) |
importance: | Undecided → High |
milestone: | none → p2 |
status: | New → Confirmed |
description: | updated |
Changed in canonical-devices-system-image: | |
assignee: | Pat McGowan (pat-mcgowan) → Alejandro J. Cura (alecu) |
Changed in snapd (Ubuntu): | |
importance: | High → Medium |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.