When USE="consolekit -policykit", consolekit support is erroneously disabled, due to bad logic on the econf command line. The current ebuild passes "--enable-console-kit --disable-console-kit" when consolekit is enabled, and policykit is disabled, which causes consolekit to be disabled, as ./configure takes the last option passed. The proper way (IMO) to fix this would be to change the line reading "$(use_enable policykit console-kit)" to "$(use policykit && echo --enable-console-kit)", which would cause the correct logic to be used.
Think it would be better to require +consolekit if +policykit is used. I believe this crazy syntax would work: policykit? ( sys-apps/hal[consolekit] ... ) Once this is done, the use_enables for console-kit can be interchanged, and things should work just fine (assuming configure always takes the latest enable/disable value passed on the command-line).
(In reply to comment #1) > Think it would be better to require +consolekit if +policykit is used. I > believe this crazy syntax would work: > > policykit? ( > sys-apps/hal[consolekit] > ... > ) I believe you're looking for bug 251179
Good call on the accidental disabling. I've fixed that in -r3. The self-reference doesn't work, I tried it. Maybe after that's approved, we'll make it cleaner.
