Re: removing some auto-generated requirements

[Bart Whiteley <bwhiteley novell com>]

I'm packaging a third-party app.  It includes some shared libs
(used as dynamically loaded modules).  These libs depend on
other libs which probably won't be present.  Since it's rare that
these libs would be loaded, the app works in spite of the missing
deps.  I don't want to remove the shared libs, because that 
would be altering someone elses product.  So, I want to include 
the shared libs, but not have RPM complain about the deps. 

Previously I wanted this feature while packaging netscape. 
We included two versions of the netscape binary: one 
that was statically linked to motif, another that was dynamically
linked to motif, just in case someone had motif and wanted 
to use the dynamically linked version.  However, autoreqprov
listed a bunch of motif deps that weren't really needed, since
the statically linked binary was also there. 

Now someone will reply and say "Why didn't you make two
netscape RPMs?"  Yes, but that's not the point. 

On Monday 18 August 2003 09:42 am, Tim Mooney wrote:
> You've piqued my curiousity, though.  Why do you want to do this?

-- 
Bart Whiteley <bwhiteley@novell.com>
Novell, Inc., the leading provider of information solutions
http://www.novell.com/