Which is still missing the point. That is most likely not available during an install. No network connection to the internet, possibly, or firewalls in between. The only source of information available, perhaps, are the packages themselves, prior to starting the install.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of John Summerfield Sent: Sunday, December 22, 2002 5:04 PM To: [EMAIL PROTECTED] Subject: Re: Determining dependencies On Sun, 22 Dec 2002, Mark Post wrote: > Except this won't do what Rich wants, either. He wants to know what other > packages depend on "this one." The only way to figure that out, from what I > can see, is to query every single package in the RPM database, and > search/grep for "this one." Now, it would probably be a good idea to save > the contents of that first phase so that you don't have to repeat it again, > since it will probably take a while. I believe this is similar to what > rpmfind.net has done for various distributions, except they've done it at a > file level. Red Hat Linux has a database of all packages that can be queried using '--redhatrequires' I don't know whether other rpm-using distroes support this, or what keyword they use. -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
