If possible, I would like to see the following QA keywords made so we can try and track what problems occur most often. The rationale for them is so that we can attempt to better educate and document the proper ways to avoid these problems. If there is a better way to do this that I am not aware of please let me know :) (A product and components? I don't know) Thanks The list: qacanfix - A trivial problem and QA will fix it if there is no response in a few days. qabadiuse - IUSE contains a bad USE flag, is missing a flag, or a flag appears to do nothing. qabaddep - The ebuild has a *DEPEND on a package that is not needed or has improper syntax. qadigestoverlap - Two ebuilds reference the same file but have conflicting digests for the file. qaglobalscope - Code is present in the global scope of the ebuild that should not be. qabaddie - The ebuild uses die in a way that causes the ebuild to needlessly fail for a user.
Done. I would send an alert out via -dev or -core (or maybe mention something to the qa-feedback@ team), so that people know about the new keywords.