I know there have been an awful lot of people who want to do this kind
of filtering.  perl, dlopen have been the primary ones I know about.

Does the filtering affect the internal per-file dependencies or just the
overall package dependencies once they are rolled together?

personally I'd like a mechanism to do this kind of filtering on a per
package basis... but so far you've talked me out of it.

--Mark

Jeff Johnson wrote:
> PLD has a patch adding a macro to specify patterns to filter internally
> generated soname dependencies.
> 
> Basically
>     %define _noautorequires libA.so libB.so
> with some regex gunk in lib/rpmfc.c to do essentially grep -v.
> 
> Should it be added?
> 
> My personal opinion is that per-pkg filtering of dependencies that are
> either mis-generated in the first place, e.g.
>     Requires: perl(the)
> or that achieve some marginally useful goal, like filtering a soname
> that is generated for a dlopen'd module that loads dynaically, is of
> marginal utility. There are many ways to solve the problem with
> existiung mechanisms in rpm.
> 
> 
> OTOH, I've always believed that there needs to be a general per-distro
> (i.e. no specfile syntax changes) filtering mechanism with patterns read
> from a file. The stopping point for the implementation is lack of an
> answer to
>     Who maintains the patterns in the file?
> 
> The PLD patch hurts nothing, but does establish a Newer! Better! Bestest!
> convention for packaging that may last for years and years, just like
> rpmrc files.
> 
> 73 de Jeff
>