Description of problem: Several packages have 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. This tracker bug will be used to track these dependencies.
To answer the question: no, it should not be necessary. We would accept patches to add some silly Provides: PolicyKit-authentication-agent and then change all the packages to require that. FWIW, this problem will disappear in early F12 with PolicyKit 1.0, when the responsibility for launching a suitable authentication agent will move to the session.
I've added Provides: PolicyKit-authentication-agent to PolicyKit-gnome now. I'll fix up the various requires tomorrow.
Also added to PolicyKit-kde-4.2.0-3.fc11.
Looks like this is now sorted out everywhere, thanks.