repoman should check for multiple inherit lines and error out in this case. According to nick's mail "Portage Info + Status Update", ebuilds should only call inherit once. I fixed 41 instances of this in the portage tree. It's clean now, but obviously people are doing it so repoman should stop them.
This should require a modification to inherit; aside from building kludgery into ebuild.sh to enable a strict mode, might be worth looking into exporting QA complaints into portage. Basically append QA complaints to a bash array, if in depend mode, export the QA complaints akin to how $dbkey is exported.
before this can happen something needs to be done about the conditional inherit problem use debug && inherit debug use python && inherit python etc...
I think carpaski mentioned that the use handling should be moved into the eclass in that case.
he did point that out ... then i pointed out that that just plain isnt possible in many cases
I can add a check to watch for multiple inherit calls, although it'll have to come after pre16 (it's about to go out the door).
Err, specifically, add a check to ebuild.sh throwing a QA notice about it. At some point repoman will need to start harvesting those QA notices.
Check went out sometime >=.51_pre16 and <=.51-rc*
