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
Yes, user must make a sane choice of selecting USE flag and thus providing information of what plugins will be compiled. There is no default USE flags for plugins and either one of input_* and output_* must be preselected before emerging. For your tinderbox needs I suggest using: USE='input_file output_http' emerge mjpg-streamer
Ehm no.. you really should have a default.
Without input/output pluging mjpg-streamer has not functionality. I'd rather force user (just like yourself) to think about proper USE flags than compile it blindly
Ebuilds have to work out of the box, to some extent. The current situation is simply _wrong_. Please fix.
Created attachment 315923 [details] new ebuild with default USE flags enabling default USE flags: +input_file +output_http
+ 28 Jun 2012; Amadeusz Żołnowski <aidecoe@gentoo.org> + mjpg-streamer-0_pre20120421.ebuild: + Default USE: input_file and output_http. +
