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 pro
Hi! We are using default useflag were it is applicable: IUSE="+bbswitch video_cards_nouveau video_cards_nvidia" The issue is that we have to make sure that at least one of the video cards is enabled also: REQUIRED_USE="|| ( video_cards_nouveau video_cards_nvidia )" And this doesn't bode well with default use, since it doesn't make sense to install the package if one doesn't have nv graphics card. Anyway it could be solved by enabling for example noveau only if none of the two options are set. But I don't think there is an easy way to express that using EAPI=4 features. Would be nice if something like this worked: REQUIRED_USE="|| ( video_cards_nvidia +video_cards_nouveau )" Well, for this case it doesn't make much sense anyway.
Does it fail if you have both enabled? Because you're not expressing that as it is. And yes one of the two still needs to be defaulted on, otherwise the default config is not working, and that's wrong.
(In reply to comment #2) > Does it fail if you have both enabled? Because you're not expressing that as > it is. It is not tested with both enabled. > > And yes one of the two still needs to be defaulted on, otherwise the default > config is not working, and that's wrong. Imho, it is not more wrong than enabling one at random. If it is really required to set one even if user hasn't done so, then REQUIRED_USE is not usable here.
Then you might want to make it an exclusive condition... and still it should work out of the box...
Regarging enabling one of them by default I am against it because *in this case* people installing this package must have VIDEO_CARDS variable properly set (if it's empty it shouldn't even need bumblebee) About making it exclusive, from a installed files point of view (that changed in existing revisions) this package should work with both enabled (or, at least, files won't collide anymore in latest revision and should work fine)
This would also cause that, for example, if we enable nvidia by default, people setting VIDEO_CARDS to "nouveau" will get both enabled if not adding explicitly "-nvidia"
