For various reasons, it is sometimes necessary to munge the
automatically-generated Perl requirements for various packages.  The
most common way to do that this I've found has been to set
_use_internal_dependency_generator to 0, create a script which did
something similar to this:

    #!/bin/sh

    /usr/lib/rpm/find-requires $* | grep -v 'perl(Business'

and then redefine __find_requires to point to this script.

As you might imagine, this technique breaks with RPM5.  The biggest
and most obvious problem being that /usr/lib/rpm/find-requires no
longer exists.  The closest thing is "/usr/lib/rpm/find-requires.perl"
which contains only "exec /usr/lib/rpm/find-requires" and similarly
fails.  Even %__find_requires points to this non-existent script.

So the question is, what's the right way to "grep out" bogus Perl
module dependencies in RPM >= 5.0?

Michael

-- 
Michael Jennings (a.k.a. KainX)  http://www.kainx.org/  <mej@kainx.org>
Linux Server/Cluster Admin, LBL.gov       Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
 "Shouldn't we help her find her way back to a place called home?"
 "Honey, she's wearing synthetic plaid.  It's a four day drive and a
  boat trip to a place called home."
     -- Sean Hayes (Jack) and Megan Mullally (Karen), "Will and Grace"