On Thu, 27 Jan 2005 17:06:10 -0600, Browder, Tom <Tom.Browder@xxxxxxxxxxx> wrote: > > -----Original Message----- > > [mailto:rpm-list-bounces@xxxxxxxxxx] On Behalf Of Jos Vos > > Sent: Thursday, January 27, 2005 4:36 PM > > Subject: Re: RPM Dependencies > > If it exists on your system but is not in an rpm, you have to > > install your package with --nodeps. > > Thanks, Jos. > > Would it not be a good feature to allow rpm to check the system for > required dependencies if they are not in rpm database? Or at least have > some kind of second-class rpm entry which just acknowledges the library > is installed (just not though a complete package)? > The second class rpm you refer to is what he meant when he said create a package that just provides libblah.so. This is what is done on Solaris (sortof). Solaris has its own packaging system and in order to deal with all the stuff that is provided in the Solaris package database there is a script that scans it and creates a package that provides all the things provided by the solaris package db. This then instaled, and then now all these dependencies are met. As for scaning the system for the dependency, think __REALLY__ slow installs; It is not a cheap process to scan the filesystem for libraries and then scan the libraries themselves and so on. All that aside, its better to simply make sure if you use a package manager, well that whats you use to install software on your system. Cheers...james > Tom Browder > > _______________________________________________ > Rpm-list mailing list > Rpm-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/rpm-list > _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
