** Description changed: 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. + 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 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”
** Summary changed: - Dig up events logic from commit history + Need a mechanism through which to receive snap changes events -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637404 Title: Need a mechanism through which to receive snap changes events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1637404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
