On 17/05/16 12:02, Jamie Strandboge wrote: > If --devmode is deemed insufficient while we wait for the gsettings work to > recommence, we can: > 1. add a new reserved 'gsettings-global' (actual name TBD) interface that > does not auto-connect. This would allow unrestricted read/write access to the > global gsettings database in the user's session > 2. when gsettings mediation lands, add app-specific gsettings access to the > unity7 interface > 3. adjust the 'gsettings-global' interface for the gsettings mediation (eg, > add the bare 'gsettings,' rule)
(3) would be my recommended approach. We should not let perfect be the enemy of good. We would LIKE to have a mediated gsettings, but we MUST unblock gsettings apps. Therefor, for series 16, we can have a general "gsettings" interface which is not mediated. We can add mediation and a more refined interface during series 16, and deprecate the general interface for series 18. Make sense? Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576308 Title: gsettings doesn't work with snap confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1576308/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
