If you are installing a tarball as part of your Process, you are, in effect, supplying the software So I would say, to shut rpm up, put a Provides: libgdb.so -----Original Message----- From: yum-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:yum-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of jeff stern Sent: Wednesday, August 31, 2005 11:09 AM To: Yellowdog Updater, Modified Subject: Re: [Yum] Re: yum install using auto-dependency checking??? okay, thank you for the careful and detailed explanation, sandra. hmm.. i guess "i wish" there were a simple/easy way to register certain files from (a vendor's) tarball with one's own rpm db, without making a separate rpm for a vendor's stuff.. but maybe this goes against the whole design of rpm.. anyway, thank you, this does make sense. i just ended up putting 'AutoReq: no' in the php.spec file in the section for the php-interbase subpackage. i also followed panu's advice and ran 'yum clean all' (see my response to his post, as well). _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum
