On 30 September 2015 at 18:33, Jussi Kukkonen <jussi.kukko...@intel.com> wrote:
> bluez5: Use upstream D-Bus policy > dbus: Use the xuser policy file > xuser-account: Take over xuser specific D-Bus policy > Please don't take the last two patches yet: I believe dbus itself does not actually have to be modified and the xuser policy file can just be a normal file in /etc/dbus-1/system.d/. I originally thought the default context policies in the services files could override the xuser user policy but this seems to not be the case: user policy always overrides default context policy. > meta/recipes-connectivity/bluez5/bluez5.inc | 5 +-- > .../bluez5/bluez5/bluetooth.conf | 17 --------- > meta/recipes-connectivity/connman/connman.inc | 1 - > .../connman/add_xuser_dbus_permission.patch | 43 > ---------------------- > meta/recipes-connectivity/connman/connman_1.30.bb | 1 - > meta/recipes-core/dbus/dbus.inc | 1 + > ...-Apply-xuser-specific-policies-if-present.patch | 33 +++++++++++++++++ > .../user-creation/files/system-xuser.conf | 15 ++++++++ > .../user-creation/xuser-account_0.1.bb | 6 ++- > 9 files changed, 55 insertions(+), 67 deletions(-) > delete mode 100644 meta/recipes-connectivity/bluez5/bluez5/bluetooth.conf > delete mode 100644 > meta/recipes-connectivity/connman/connman/add_xuser_dbus_permission.patch > create mode 100644 > meta/recipes-core/dbus/dbus/0001-Apply-xuser-specific-policies-if-present.patch > create mode 100644 > meta/recipes-support/user-creation/files/system-xuser.conf > > -- > 2.1.4 > >
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
