| Subject: | prereq_matches_use, build_prereq_matches_use should respect other data in META |
If a prereq is listed in optional_features, or as a recommends or suggests prereq, this should be enough to satisfy the metric. Static code analysis cannot always determine if a 'use' or 'require' statement is always executed, so it should be sufficient to accept the module being mentioned *somewhere* in META as a prereq.
(http://cpants.cpanauthors.org/author/ETHER has some failing cases that would pass for this. I can find more specific examples as needed.)