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
hmm will have a look at that then ;)
hmm now i should know which is supposed to be default .. hmm shall i go for sqlite which is smallest or mysql which i think was first db supported by dbmail ... also .. shouldn'T the default dep be already sorted by this: !mysql? ( !postgres? ( !sqlite3? ( >=dev-db/sqlite-3.0 ) ) ) i'll try to find out what hte preferred db is (i couldn'T find anything on the webpage) if not i prolly go for either mysql or sqlite (even though i use postgres ;))
any news on this ?
Created attachment 240343 [details] 2.2.16.ebuild I don't use dbmail but the attached ebuild should work. Please test before production.
checked the euild and it looks good. thanks for helping out i am on a bit tight schedule atm Commited as 2.2.17
