Description of problem: gnome-power-manager has a hardcoded dependency on PolicyKit-gnome. Is this really necessary? In the KDE spin, we would like to ship PolicyKit-kde instead of PolicyKit-gnome. PolicyKit-kde also implements the org.freedesktop.PolicyKit.AuthenticationAgent service. (Note that gnome-power-manager is not included on the current KDE spin.) Version-Release number of selected component (if applicable): gnome-power-manager-0:2.25.91-1.fc11 How reproducible: Always Steps to Reproduce: 1. repoquery --repoid=rawhide --whatrequires PolicyKit-gnome Actual results: gnome-power-manager requires PolicyKit-gnome. Expected results: gnome-power-manager does not require PolicyKit-gnome. Additional info: Maybe a common Provides in both PolicyKit-gnome and PolicyKit-kde is needed?
(In reply to comment #0) > Maybe a common Provides in both PolicyKit-gnome and PolicyKit-kde is needed? Sure, a provide of SessionAuthenticationAgent would probably be the best idea.
In Rawhide, both PolicyKit-gnome and PolicyKit-kde now have: Provides: PolicyKit-authentication-agent so you can require this instead of PolicyKit-gnome.
Actually, gnome-power-manager does use the PolicyKit-gnome bits: return polkit_gnome_action_create_button (prefs->priv->default_action); So we wont get rid of the library dependency against PolicyKit-gnome here.
We can live with that one as well.
That said, isn't that stuff in PolicyKit-gnome-libs? If it is, we could still avoid dragging in the main package. But gnome-power-manager isn't going to be used on the KDE spin either way.
I guess you are right about the -libs. Anyway, the package only has an explicit requires for PolicyKit-authentication-agent now.