Comment 13 for bug 1015564
Revision history for this message
| Victor Martinez (victored) wrote Re: Unity and Sound Menu support should be checked at runtime | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Kurt, here are my replies:
> This of course does not mean libunity won't be installable at all, but I think having MPRIS as backup is still a good idea.
I agree with you on this. It would be a dumb action to drop MPRIS support in distros like Arch or Fedora just because we decided to go with libunity.
> So either only instantiate the MPRIS client in case libunity can't be loaded or remove the MPRIS functionality from UnityIntegration and always load MPRIS client.
If we already linked the player against libunity, and the it's not found, bad things will happen. There's not much we can do to avoid it at runtime. We could do this safely if UnityIntegration were a plugin (which is easy to do by using libpeas). I believe there will be some work on basic plugin functionality soon, so this is actually possible and should be considered. We could then disable the MPRIS plugin if the UnityIntegration plugin is enabled.
The nice thing with plugins is that distros can package the plugins that make sense and are installable in their context. For instance, the MPRIS plugin wouldn't be built in Ubuntu.
What do you think?