Hello, You're receiving this canned (template-based) bug report because I found an annoyance with a package during my tinderbox run. The package in question is checking for one out of a series of USE flags to be enabled, likely because these are multiple selectable backends, but it currently does not use the EAPI=1 feature of default USE flags to work out of the box. You can see in my blog post in the URL field why that's a problem, and how to address the issue. It would be very kind of you for both users and developers working on automated reporting, if the ebuild for the package enabled by default at least one backend (more might be enabled if needed). Please note that sometimes you don't feel the need for this because the desktop profile already enables some of the USE flags, but please consider the idea of enabling them nonetheless, it would help a lot. Thanks, Diego
*** Bug 305983 has been marked as a duplicate of this bug. ***
Created attachment 243891 [details] ebuild adding default USE flag support. Since this is a p2p client, I think most users would expect a gui client to be built by default. Users that want it run as a daemon or via remote access will probably be more attentive to their USE flags.
Created attachment 243911 [details] ebuild adding default USE flag support. Since this is a p2p client, I think most users would expect a gui client to be built by default. Users that want it run as a daemon or via remote access will probably be more attentive to their USE flags.
Fixed in 2.3.1, thanks, will close when it is stable
