> If there are some common files that can be shared between the two implementations, we could create an account-plugins-common package, which could be used by both. If the maintainers of kaccounts-providers think that this is the case, let them comment here.
The problem with this is client keys and client secrets. We could possibly supply these at runtime from some place else (like from ubuntu- online-accounts), but that just recreates the libaccounts elsewhere. The actual problem is AppArmor and similar things, because mission- control-5 is restricted. With the new file locations the accounts-sso plugins just doesn't work as it gets blocked access to the provider/service files and libaccounts-glib just returns empty accounts list. This requires shipping AppArmor and similar config files (simply telling distros you need to include this patch is _not_ going to work; speaking from experience). Imho the best solution would be to have a filtering on libaccounts-glib level. The providers could have a "<showOnlyIn>kde"</showOnlyIn>. That way all those files could live in the same dir with prefixed filenames and libaccounts-glib would always return the correct list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540135 Title: Make this metapackage conflict with kaccounts-providers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1540135/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
