Description of problem:
/usr/lib/rpm/find-requires.perl creates requirement lists that include
conflicting packages.

Version-Release number of selected component (if applicable):
rpm-build-4.2-0.69

How reproducible:

Always.

Steps to Reproduce:
1. In my case, produce a mod_perl application, or port one, that can
be used in MP1 and MP2.  This requires code like the following:

use constant MP2 => $mod_perl::VERSION >= 1.99;
if (MP2) {
    require Apache::Const;
    Apache::Const->import(-compile => qw(:common));
    use ModPerl::Registry ();
}
else {
    require Apache::Constants;
    Apache::Constants->import(qw(:common));
    use Apache::Registry ();
}

2. package this code
3. attempt to install this code.
  
Actual results:
The resulting package, if find-requires.perl is used, requires BOTH
perl(Apache::Registry) and the replacement perl(ModPerl::Registry),
and they both cannot be installed concurrently.

Expected results:
On Mod_Perl 2 systems, where Registry is in ModPerl, --requires would
conceivably only include that requirement.  The converse would be true
for MP1-based systems.

Additional info:

Nah, I've not got high hopes on this one.  I mean, the workaroudn of
hand-compiling requirements lists is an option, if a terribly
distasteful one.