Having USE="bittorrent bittorrent-external" for kde-base/kget-4.2.2 seems quite logical. Currently the ebuild dies because of it. use.local.desc doesn't point out why there is a conflict, and one would assume that IUSE="bittorrent" implies building bittorrent support generally, whereas IUSE="bittorrent-external" would mean depending on some other package to provide that support. kde-base/kget:bittorrent - Enable embedded bittorrent transport plugin kde-base/kget:bittorrent-external - Enable external bittorrent transport plugin via ktorrent I think the logic should be changed like this: USE=" bittorrent -bittorrent-external" - Build internal plugin. USE=" bittorrent bittorrent-external" - Build external plugin. USE="-bittorrent +bittorrent-external" - Build external plugin. USE="-bittorrent -bittorrent-external" - Build neither. This way the build need never die. The user could be warned about what kind of bittorrent support plugin is built, and that should be all we need to do.
Fixored. Thanks for report. Now i should fix the ktorrent but it wont be right now i need to find some time for it...
That logic in USE flags and to die with message was my idea. I agree that proposed solution is better (well, it's usually better not to die ;) Thanks
